Webglcontextlost debugging help.

[Bob Blaine]

Hi,

I'm looking for advice on how to, or if we can, figure out why we are getting a webglcontextlost event in an application written on top of the Chromium Embedded Framework.. 

The message in the WebGLContextEvent  that's sent to our listener is blank , however, there is a message on the console: "WEBGL: CONTEXT_LOST_WEBGL: loseContext: context lost". That kind of suggests to me that it's being forced.

As far as we know we are the only usage of WebGL in the application, and this only occurs on Linux with hardware graphics.

Is there a way to figure out what's triggering the context lost event?

Any suggestions would be appreciated.

[Ken Russell]

Can you open the about:gpu page in a new tab within your application? That should contain additional logs which might be helpful.

In general on Linux context loss will only happen if the graphics card hung and the OpenGL extension GL_KHR_robustness reported and recovered from that, or Chromium's GPU sub-process crashed and restarted.

Is it possible for you to provide a test case which runs in regular Chromium rather than in your app?

-Ken

--
You received this message because you are subscribed to the Google Groups "WebGL Dev List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webgl-dev-lis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/webgl-dev-list/8cde1f4f-2d7c-4514-97e8-3de6bac6cb68n%40googlegroups.com.

--

I support flexible work schedules, and I’m sending this email now because it is within the hours I’m working today.  Please do not feel obliged to reply straight away - I understand that you will reply during the hours you work, which may not match mine. (credit: jparent@)

[Bob Blaine]

Hi Ken,

Sorry for the delay in response. Thanks for your suggestions. I'm not able to figure out a way to reproduce this outside of our app and in fact, if we redirect our web page to a Chrome browser, the functionality works. I'm thinking that since our app is based on an older version of the Chromium Embedded Framework, the problem may have been resolved and we just need to await an update on that. For now, it seems that we can just request a new context and continue on.