Error CONTEXT_LOST_WEBGL

[Dad72]

Hello,

Since the last update of Chrome (Version 69.0.3497.81)  that I made yesterday, I regularly receive his errors that makes the Babylon scene crash?

Can someone explain to me his mistakes that I have never had before ?  I use only one engine per canvas, but I have several canvas on different tab and therefore several engine to load. Could this be the problem? It's annoying because for my editor I would like to make an engine for each editor integrate (animations, terrains, actors, particles, articles ...)

Is this Chrome that has a bug? Anyone get his mistake too? what do you want to say?

Quote

WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
 BJS : WebGL context lost.

It looks like the latest version has memory leaks.

Thank you

[Guest]

This is not memory leak  This is DEFINITELY a chrome bug (remember that 69.0.3497.81 is a beta so open to bugs)

By the way, I'm on the same version but I have no crash. Can you repro with a scene on our homepage or on the PG?

[Dad72]

It's very random, I do not know how to reproduce it. that happens when I paint on a dynamicTexture, or when with animate characters or anything else in very random ways.

Maybe because I create several engines too.

I read somewhere that this could be Chrome's memory leak.

I will go back to the previous version of Chrome to avoid mistakes.

[Guest]

if you have a repro, let me know because I could file a bug to chrome as I do not want to have this issue on their non beta product 

[Dad72]

Ah and this is not a Beta version anymore, she came out yesterday apparently

https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html

[Dad72]

I do not know if it's related, but before with this demo scene I was at 60 fps, but with this version of Chrome I turn between 5 and 10 fps if we zoom back.

And yet my graphics card is a GTX 1050 Ti 4 GB memory

http://www.babylonjs-playground.com/#3YFJ5R#0

On this scene, I am between 1 fps

http://www.babylonjs-playground.com/#1OQFOC#64

 

[Sebavan]

Oh, let me look at it as it could be my latest octree changes, It looks like both scene are using it.

[Dad72]

After I do not know if my problem is related to that. I'm just stumbling over this problem with Octree looking for a scene that would crash with the new version of Chrome. But I do not find why. It's very random, but very regular on my big project editor of MMORPG.

I hope to find and understand, otherwise I will resume the previous version that did not crash.

[Dad72]

The mistake I get is here :

};
        ;
        /** @hidden */
        Engine.prototype._createTexture = function () {
            var texture = this._gl.createTexture();
            if (!texture) {
                throw new Error("Unable to create texture");
            }
            return texture;
        };

Quote

Tools._WarnEnabled @ babylon.max.js:9912
(index):1 WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
babylon.max.js:9912 BJS - [20:38:13]: WebGL context lost.

Uncaught Error: Unable to create texture
    at Engine._createTexture (babylon.max.js:14547)
    at new InternalTexture (babylon.max.js:29669)
    at Engine.createDynamicTexture (babylon.max.js:14866)
    at e.DynamicTexture._recreate (babylon.max.js:68918)
    at e.DynamicTexture.scaleTo (babylon.max.js:68939)
    at e._onResize (babylon.gui.min.js:1)
    at Observer.callback (babylon.gui.min.js:1)
    at Observable.notifyObservers (babylon.max.js:8388)
    at Engine.setSize (babylon.max.js:12782)
    at Engine.resize (babylon.max.js:12757)

You can reproduce the error here. To do this, load a terrain, activate the edit mode, and select textures to paint.

Choose a first texture and paint 10 seconds, then choose another texture, paint 20, 30 seconds, see more. That should crash with screen black

Link (I put the babylon.max.js) : http://www.babylon.actifgames.com/TerrainEditor/index.php

By the way, there is one " ;  " too much above /** @hidden **/

[Sebavan]

Do you happen to have the same with a version from 2 weeks ago ?

just to ensure it comes from chrome and not my changes ?

[Dad72]

For Octree I do not know if it worked better 2 weeks ago.

For the WebGL error, this produces since yesterday that I updated the browser.

[Sebavan]

ok cool I ll dig deeper, and unfortunately I can see the crash now I updated...

[Dad72]

OK, thanks to investigate the error.

[Sebavan]

About the context lost I have a repro: https://playground.babylonjs.com/#Y6XVXY#5

This is pretty convoluted (Rather Large Canvas in Canvas in Canvas) and only happen on chrome69 so far. @Deltakosh will create the chrome ticket tomorrow.

I am now looking at the octree.

[Sebavan]

We probably identified the octree issue as well, this will all be done tomorrow ?

[Dad72]

Thanks for the PG, I could not identify the problem myself

[Dad72]

Is there a workaround that can be done in Babylon until it is fixed in Chrome? I end up with all my editors broken because of this. I planned to release my MMO editor in the month, but I have the impression that this major Chrome bug will stop me. . Thank you Deltakosh if you can find a workaround.

Not so stable their Chrome 69 at once. But I admit that she is more pretty.

Edit : This also happens without doing anything, donating to more than one canvas on a page or the creation of a screenshot if you wait a while

[Guest]

Yes this is a really nasty bug in latest version of Chrome and I have no idea how to work around it.

It seems that reducing the size of the texture could help

[Guest]

@Dad72: Here is the bug tracker https://bugs.chromium.org/p/chromium/issues/detail?id=881866

Let's hope they will fix it asap!

[Guest]

octree should be good by the way

[Dad72]

Cool. Thanks. Yes I hope that it will correct quickly and publish update at once, because it is a really awkward and major bug for a so-called stable version.

[Dad72]

Even worse this bug. if I open the console and wait a few seconds, I crash repeatedly without doing anything : 

 https://playground.babylonjs.com/#Y6XVXY#5

[Guest]

Also for the performance issue: 

 

 

[Guest]

Chrome bug ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=881977

[Dad72]

Hello,

@Deltakosh It's strange, I have more crash and yet no update of Chrome. Maybe something has been fixed in the engine ? The problem did not come from Chrome, so. 

@Sebavan On the other hand for Octree, there is better, but I understand not something.
Previously I was shooting at 60FPS with a GTX 960 graphics card this scene and now I was shooting at 45 FPS In the center and 10 FPS with zoom back with a more powerful graphics card GTX 1050.

I guess there is some problem yet.

http://www.babylonjs-playground.com/#3YFJ5R#0