Event 'webglcontextlost' not fired even when there is a message in console regarding the same
Reported by
luv.raja...@gmail.com,
Dec 4
|
|||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
Steps to reproduce the problem:
1. Loading a large obj file using Three.js and applying textures
2.
3.
What is the expected behavior?
What went wrong?
CONTEXT_LOSE_WEBGL: loseContext: context lost in console and 3D model disappears. I tried listening to this event using 'webglcontextlost' event listener but this event doesn't fire.
Did this work before? No
Chrome version: 70.0.3538.110 Channel: stable
OS Version: 10.0
Flash Version:
I am using below snippet to catch that event but it doesn't fires up-
renderer.domElement.addEventListener('webglcontextlost', function(e) {
setTimeout(renderer.forceContextRestore, 100);
});
,
Dec 4
,
Dec 5
,
Dec 5
The GPU process is probably crashing and causing the WebGL context to be lost. This is non-recoverable to avoid denial of service issues. I suggest you ask on the Three.js issue tracker why this is happening and provide a test case. Your model is probably too large, uses too large textures, or something similar.
,
Dec 6
Is there any callback I can rely on when this happens?
,
Dec 7
Not if your content is crashing Chrome's GPU process. Please reduce your test case as much as possible and discuss it with the Three.js community. If you can't figure it out then please file another bug here. Always include the contents of your about:gpu page from Chrome (copy/paste plaintext, no formatting) when filing graphics bugs here. Thanks. |
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 4