[Webkit-unassigned] [Bug 239076] New: [iOS] Stack overflow in -[WKFullScreenWindowController _exitFullscreenImmediately]

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=239076

            Bug ID: 239076
           Summary: [iOS] Stack overflow in -[WKFullScreenWindowController
                    _exitFullscreenImmediately]
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ajuma at chromium.org
                CC: bfulgham at webkit.org, jer.noble at apple.com,
                    simon.fraser at apple.com, zalan at apple.com

Created attachment 457263

  --> https://bugs.webkit.org/attachment.cgi?id=457263&action=review

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220411/2193b1aa/attachment-0001.htm>