Bug 262628

Summary:	WebGL: context lost - iOS 17 Safari
Product:	WebKit	Reporter:	travis
Component:	WebGL	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED DUPLICATE
Severity:	Critical	CC:	ahmad.saleem792, ap, dino, josselin.guillozet, kbr, kkinnunen, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	Safari 17
Hardware:	iPhone / iPad
OS:	iOS 17

Description travis 2023-10-04 09:22:11 PDT

We have a very lightweight Unity game that we've been running pretty successfully on mobile web. That said, we've just run into a pretty show-stopping issue with iOS 17 Safari. The game will work totally fine on iOS 17 Safari - but then after some combination of backgrounding, using other sites and other apps (not totally sure the exact repo) - it errors with:

"WebGL: context lost"

At this point, no matter how many times I refresh, I will always get this error. Force quitting browser and event resetting the device doesn't seem to recover it. I've also tried to do different combos of compressed builds - and nothing seems to work. The one thing that does recover is clearing the safari cache. We never encountered this issue in Safari 16 - only 17. 

It seems like this might be an issue beyond Unity - see this thread. Apparently threejs is experiencing the same: https://developer.apple.com/forums/thread/737042

Comment 1 Ahmad Saleem 2023-10-04 12:33:47 PDT

I think it seems to be fixed in Safari 17.1:

https://developer.apple.com/documentation/safari-release-notes/safari-17_1-release-notes#WebGL

Comment 2 Josselin Guillozet 2023-10-10 08:46:18 PDT

We also observed some "WebGL: context lost" at least on iPhone X with iOS/Safari 16.7 after moving the browser to the background.
Once we get the error, we can't create any stable WebGL context until we clear the browser data.
More generally in production, we've noticed a sharp increase of WebGL related error on Safari 16.7 and 17 (Unfortunately, we don't have specific logging to check whether it relates to "WebGL: context lost").

Comment 3 Radar WebKit Bug Importer 2023-10-11 09:23:12 PDT

<rdar://problem/116813694>

Comment 4 Ahmad Saleem 2023-10-29 20:16:16 PDT

Safari 17.1 is released now, do we need to keep this open since it shipped with WebGL fix.

@Alexey - any input?

Comment 5 Alexey Proskuryakov 2023-10-30 08:31:31 PDT

Indeed, this should have been duped to bug 261313.

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