Safari, WKWebview Crash in iOS 15 Beta2

We are servicing html5 games. I got a report from a user, and I heard that it will be whited out shortly after entering the game lobby in ios 15 beta. It was not a problem in iOS 14, but in iOS 15 beta2, it is forcibly terminated shortly after entering the lobby. Safari and WKWebview are all the same, and the same problem occurs regardless of the device. The devices I tested were ipad mini4, iphone 11, iphone 12.

Seeing that it does not crash when the light effect tween is turned off, I think that the amount of memory available to the GPU for rendering has decreased.

Does anyone have similar symptoms related to html5 games?

Answered by adrianli in 684348022

try to disable option "GPU Process: Canvas Rendering". we don't know why it's on by default on beta 4 and 5.

yes, we have experienced Safari performance problem on ios 15 too.

even worse on beta 5, using a game from https://www.pixijs.com/gallery https://tooncup.cartoonnetwork.co.uk/home/

it gets stuck at the entering game, while there is no problem on ios 14.

Accepted Answer

try to disable option "GPU Process: Canvas Rendering". we don't know why it's on by default on beta 4 and 5.

  1. If there is a large amount of JavaScript to be parsed at once, the JavaScript engine seems to be very slow.
  2. Create a Graphics object using a path with many points and use it as a mask, and if you move it, memory leak occurs and the webview dies. ( in Cavas mode )
  3. If you do not disable GPU Process:Canvas Rendering when rendering in WebGL mode, it may become stuck when moving the scene. (tested in safari)

How can we fix this from code in WKWebKit?

It seems the trigger is unicode string. We made a demo app and it worked in iOS15. After we put a unicode string it started to crash.

How can we fix this from code in WKWebKit?

I get the problem that video only sound but no picture,in wkwebview iOS 15, both in our app and safari with device ipad 6, ipad mini 5 and iphone 8p i disable option "GPU Process: Media", and in safari it get right. so how can we fix this from code in WKWebKit?

This new feature completely broke my app - which is a WKWebView with a large canvas. Performance is incredibly slow and renders the app useless. Worked great in iOS 14..

How can we disable this setting in a WKWebView?

Why would it be that that canvases performed better on the CPU but Apple dropped that as the default and switched to GPU processing? Wouldn't the switch be to increase performance?

Really concerned about the future of my app if we can't disable this 'feature'. Will the setting eventually go away and this will be the default?

We have the same problem. Our iOS and iPad app is built with WKWebView technologies and on iOS 15 and iPadOS 15 we now have huge problems with performance and stability because of this GPU option by default (on the previous iOS/iPadOS versions it's fine).

And we couldn't find a way how to turn this GPU option off in the app. Apple team, we need your help with this, a lot of users struggle.

I reported it to apple, but this issue still keeps ignored. Monopoly companies are always willful, what can you do

same problem. Using canvas. Background the page then come back and everything is almost, but not quite, frozen. Users will have no clue how to fix this themselves.

We have the same issue, bug reported - FB9687881, please take a look

We have similar issue. Our app using xTerm.js in WKWebview encounters character disappear and frequently crash.

It is all good on Safari on all devices and Simulators, and also on SFSafariViewController. It just happens in WKWebview on iPadOS 15.1 and iPhone Simulator with iOS 15.0 according to our test.

So we guess some features in WKWebview (possibly Canvas) have different behavior but we don't know what are they.

Any updates? Canvas in WKWebView are unusable.

Safari, WKWebview Crash in iOS 15 Beta2
 
 
Q