Open
Bug 1502463
Opened 7 years ago
Updated 3 years ago
Multiple Context WebGL
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: david.pe, Unassigned)
Details
(Whiteboard: gfx-noted)
Attachments
(1 file)
|
109.35 KB,
image/jpeg
|
Details |
Hello,
When I load one or more BabylonJS engine, in the console, that says that I exceed 16 WebGL Context.
Maybe it's because I use more than one canvas, but I only load one WebGL engine per canvas.
For example in Google Chrome and Opera, my 3D scene gets 60 FPS, but with firefox, I get 30FPS.
If I only load 1 single engine or 1 canvas, my FPS goes back to 60 in firefox.
In the attached file, I have 8 engine to load and that tells me that I have 16 WebGL context.
Sorry for my bad english
Thanks
For information, the console errors this is with this line of code.
this._gl = (canvas.getContext("webgl2", options) || canvas.getContext("experimental-webgl2", options));
Updated•7 years ago
|
Component: General → Canvas: WebGL
Product: Firefox → Core
Comment 2•7 years ago
|
||
What's likely happening is that you have 16 other webgl contexts open in other tabs. If you have 16 canvases though, yeah, we'll start destroying them.
We can probably raise or remove this limit.
Severity: critical → normal
Priority: -- → P3
Whiteboard: gfx-noted
Hi,
No I did not have 16 context webGL but 8 loaded on the same browser tab, I only had one open tab.
I was loading a WebGL context by canvas, and I needed 8 canvas, but I got this error as what was loaded.
The double is calculate, which seems to me to be the bug.
Thank you for responding after 3 months.
In fact to clarify, if I have 2 canvas on my page that loads a context WebGL, I have this error as 16 context WebGL loaded, which is not the case.
On another browsers I do not have this error. I am now using Opera and Google Chrome.
Updated•6 years ago
|
Summary: Multiple Contexte WebGL → Multiple Context WebGL
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•