Note that other models/webpage does reproduce the models (it's not isolated)

ie: see that model on chrome 62 https://sketchfab.com/models/c80711150dec473dba5b800450d81468
then try it on any other browser/os

To give more informations, I don't think it's related to sketchfab or this model in particular.

The scenario is rather :
- browse webgl stuffs
- experience a webgl crash (which happens more often than it probably should with last chrome 62 release, see https://bugs.chromium.org/p/chromium/issues/detail?id=778188)
- then if you visit some page with webgl, it's super slow and the cpu goes 99%

Unfortunately, it doesn't happen in a consistent way.
Sometimes there's a webgl crash and just restarting the page will solve the issue

If this is caused by crashes, then it's just because we've fallen back to software rendering with SwiftShader. You can double check this in chrome://gpu.

The fix for this issue is to fix the GPU process crashes in  issue 778188 .

Specifically, if the GPU process crashes 3 times, we force software rendering of WebGL.

Thanks, very informative anwser, help a lot.

Unless there is another way, we'll rely on webgl debug renderer extension to prevent user trying sketchfab in software render mode.
(even high end cpu desktop it's too slow for sketchfab viewer)

> "GPU process crashes 3 times"

Does that count if we trigger lostContext using the lostContext extension ?

> Does that count if we trigger lostContext using the lostContext extension ?

Nope, that only takes down the WebGL context. The 3-strikes rule only applies to actual, native crashes (like segfaults and so on) in the GPU process. This rule is just to mitigate attacks by disabling the attack surface.

The WebGL context creation attribute "failIfMajorPerformanceCaveat" can be set to true to avoid using SwiftShader as a fallback.

Thanks for the informations, it really helps.

Glad to know we can rely on lostContext.
W'ere thinking/planning/testing to release reliably all resource this way on "invisible" tabs so that "visible" tabs has everything. (now that we support restorecontext)

Ah, I knew webgl had something for that but forgot about this one, then we'll add "failIfMajorPerformanceCaveat" support on sketchfab asap. 


Thanks again for first class answer/support !

I suspect that the reason for the GPU process crashes is  Issue 778689  and am duplicating this into the other bug.