| Summary: | [iOS] Stack overflow in -[WKFullScreenWindowController _exitFullscreenImmediately] | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ali Juma <ajuma> | ||||||
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | RESOLVED DUPLICATE | ||||||||
| Severity: | Normal | CC: | bfulgham, jer.noble, simon.fraser, webkit-bug-importer, zalan | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
Created attachment 457264 [details]
Crash report from iOS 15.5 beta
*** This bug has been marked as a duplicate of bug 239744 *** |
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.