On iOS 10, GLTF-WebGL app crashes, Application is build using WKWebView

13
votes

I am working on 3D model in javascript & using GLTF webGL to render 3D model in iOS. I am loading this model using WKWebView in Ipad Air/Ipad Air 2.

This configuration/application works perfect in IOS9, But after upgrading OS to IOS 10 my application get crashed. I am trying to debug same on Xcode then showing following error message :

Error Message:  "#WK: Unable to acquire assertion for process 0".

We have tried same thing using UIWebView in IOS10 it is working but performance is low (application working slow).

Additional information :

  1. GLTF-WEBGL link to open 3D model https://github.com/montagejs/glTF-webgl-viewer.git.
  2. When I changed offsetHeight to scrollHeight, able to view the 3D model, but crashed after some time.

Any body have any cue to debug WebGL issues on iOS 10 ?

2
javascriptwebglios10wkwebviewgltf
I just came upon the same problem, but I'm not using WebGL. My client is using storyline SCORM content and having the same error. – Putz1103
Have you tried other glTF viewers? It looks like that montagejs one dates back to glTF 0.8 in 2014. There were breaking changes between glTF 0.8 and glTF 1.0. – emackey
Thank for replaying emackey, – user3587692
I have tried with other glTF0.8 but still facing the same problem. Is this crashed issue is happened for height width properties. – user3587692
Its not a WebGL issue, as this is not a WebGL error message. – LJᛃ

2 Answers

2
votes

Please check the log in console whether you can find anything. I had the same error "Error Message: "#WK: Unable to acquire assertion for process 0".", and I found it was because I used css property -webkit-overflow-scrolling, this property consumed a lot memory, and last WebKit process crashed.

0
votes

I'm getting the same error, though I'm not using WebGL at all. I am, however, using GPUImage2.

Are you using the Safari Web Inspector on your host machine? Based on my experience and some anecdotal & related evidence, I think the problem is a bug in some combination of that and WKWebView on iOS 10.

It's not an ideal solution, but not using the web inspector has prevented WKWebView from crashing for me.

(Interestingly, it doesn't crash if I use the web inspector but am not doing anything GPU intensive.)