Bug 239000 - U+0622 + U+064E crash browser: "a problem repeatedly occurred"
Summary: U+0622 + U+064E crash browser: "a problem repeatedly occurred"
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-08 07:50 PDT by mustafa.0x
Modified: 2022-04-08 14:35 PDT (History)
4 users (show)

See Also:


Attachments
screenshot (12.66 KB, image/png)
2022-04-08 11:46 PDT, mustafa.0x
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description mustafa.0x 2022-04-08 07:50:14 PDT
```
<meta charset=utf-8>
آَ
```

Release 142 (Safari 15.4, WebKit 17614.1.5.16)

This combo is a typo, but even so, a browser crash is unwarranted. Similar combos may also cause crashes.
Comment 1 zalan 2022-04-08 08:39:14 PDT
Thanks for reporting this issue. Unfortunately I am not able to reproduce the crash by just copy-pasting the "آَ" content and neither by constructing a test case by using the associated HTML entities (&#1614;&#x64E; etc). Would you mind attaching the actual markup that reproduces this crash, please? Thanks!
Comment 2 mustafa.0x 2022-04-08 08:44:05 PDT
It seems that you didn't copy the <meta> tag as well.

Copy and paste this in the address bar:

data:text/html,<meta charset=utf-8>آَ
Comment 3 Simon Fraser (smfr) 2022-04-08 09:41:27 PDT
What OS version are you reproducing this on? Can you find a crash log (via Console.app) and attach it?
Comment 4 mustafa.0x 2022-04-08 11:46:51 PDT
Created attachment 457104 [details]
screenshot

Occurs on macOS 12.2 and also on iOS 15.

It doesn't crash the browser, just the renderer.

Here's a codepen:
https://codepen.io/mustafa0x/pen/QWarrZe
Comment 5 Alexey Proskuryakov 2022-04-08 14:35:58 PDT
This is the same stack trace as rdar://87542346, which got fixed in macOS 12.3. I can reproduce on macOS 12.2.1 byt simply opening this bugzilla page.

The fix was not in WebKit, but in underlying system frameworks.