Bug 239076 - [iOS] Stack overflow in -[WKFullScreenWindowController _exitFullscreenImmediately]
Summary: [iOS] Stack overflow in -[WKFullScreenWindowController _exitFullscreenImmedia...
Status: RESOLVED DUPLICATE of bug 239744
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-04-11 09:58 PDT by Ali Juma
Modified: 2022-05-06 12:51 PDT (History)
5 users (show)

See Also:

Attachments
Test case (432 bytes, text/html)
2022-04-11 09:58 PDT, Ali Juma 		no flags Details
Crash report from iOS 15.5 beta (75.45 KB, text/plain)
2022-04-11 09:58 PDT, Ali Juma 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ali Juma 2022-04-11 09:58:15 PDT 
Created attachment 457263 [details]
Test case

This happens when calling window.alert() very soon after calling webkitRequestFullscreen(). On my iPad mini 4 running iOS 15.5 beta, calling alert() ~250ms after webkitRequestFullscreen() triggers this bug at least 50% of the time. I can also reproduce on iOS 15.4.

Steps to reproduce in Safari with the attached test case:
1) Tap the "Launch fullscreen" button. This will enter fullscreen and schedule a call to alert() in 250ms.

At least 50% of the time, this will crash the UIProcess with a stack overflow in -[WKFullScreenWindowController _exitFullscreenImmediately].

If it doesn't work the first time, reload the page and try again.

This does not cause a crash on Safari on macOS, but sometimes causes the entire screen to go blank for several seconds.
Comment 1 Ali Juma 2022-04-11 09:58:42 PDT 
Created attachment 457264 [details]
Crash report from iOS 15.5 beta
Comment 2 Radar WebKit Bug Importer 2022-04-11 11:53:17 PDT 
<rdar://problem/91580484>
Comment 3 Ali Juma 2022-05-06 12:51:31 PDT 

*** This bug has been marked as a duplicate of bug 239744 ***