Description
HTML5 fails to compile on Mac when built for shipping in binary
I did not see this when packaging for development yesterday
Does not occur in 4.14.3
The error appears to be WebGL related
Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. GitGud.html:228:15 Successfully compiled asm.js code (total compilation time 9016ms; stored in cache) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:83964 Error: WebGL: texImage2D: With format DEPTH_COMPONENT24, this function may only be called with target=TEXTURE_2D, data=null, and level=0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:329126 Error: WebGL: texSubImage2D: The specified TexImage has not yet been specified. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:313154 Error: WebGL: drawElements: Drawing to a destination rect smaller than the viewport rect. (This warning will only be given once) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:215127 Error: WebGL: framebufferTexture2D: `level` must be 0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: clear: Framebuffer must be complete. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: clear: Framebuffer must be complete. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: clear: Framebuffer must be complete. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: clear: Framebuffer must be complete. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 Error: WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) 7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:304222 uncaught exception: ASM_CONSTS<@blob:http://localhost:8000/7a5e7474-feb4-2243-a4cc-b332d1c3f9fe:1:28129
and
Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. GitGud.html:228:15 Successfully compiled asm.js code (loaded from cache in 741ms) f229ad23-903a-d94c-b0c6-ae8b86be2a8e Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:83964 Error: WebGL: texImage2D: With format DEPTH_COMPONENT24, this function may only be called with target=TEXTURE_2D, data=null, and level=0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:329126 Error: WebGL: texSubImage2D: The specified TexImage has not yet been specified. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:313154 Error: WebGL: drawElements: Drawing to a destination rect smaller than the viewport rect. (This warning will only be given once) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:215127 Error: WebGL: framebufferTexture2D: `level` must be 0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: clear: Framebuffer must be complete. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: clear: Framebuffer must be complete. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: clear: Framebuffer must be complete. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222 Error: WebGL: clear: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: clear: Framebuffer must be complete. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:234511 Error: WebGL: framebufferTexture2D: `level` must be 0. f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:237959 Error: WebGL: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd7) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222 Error: WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) f229ad23-903a-d94c-b0c6-ae8b86be2a8e:1:304222
Steps to Reproduce
- Create a new BP FPS project with no starter content
- When in editor set File > package project > build configuration > Shipping
- Then hit File > Package Project > HTML5
- Select a location to package the project to
- When the package is complete navigate to the containing folder and run RunMacHTML5LaunchHelper.command
- Open a Firefox browser window and go to *[Link Removed]
- Select ProjectName-HTML5-Shipping.html
Results: The project fails to compile
Expected Results: The project compiles cleanly
Have Comments or More Details?
There’s no existing public thread on this issue, so head over to Questions & Answers just mention UE-40601 in the post.
I’m probably super dumb and overlook some tiny detail that messes up everything I do.
Browser:
Firefox 35.0
Chrome 40.0.2214.91 m
Code:
<!DOCTYPE html><html> <head> <title>Nothing to see here</title> <style> body { background-color: #000; } canvas { background-color: #222; } </style> </head> <body onload="init();"> <div align="center"> <canvas id="game-canvas" width="512" height="384"></canvas> </div> <script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></script> <script src="pixi.dev.js"></script> <script type="text/javascript"> <!-- function init() { var stage = new PIXI.Stage(0x0168b1); var renderer = PIXI.autoDetectRenderer(512, 384, $("#game-canvas")); renderer.render(stage); } --> </script> </body></html>
This is pretty much the exact code that the first tutorial ever shows.
WebGL creation failed and Expected behaviour
What I have here is a javascript function called init that is being called by the body onload event which I expect to run after things such as pixi.dev.js and jquery have loaded.
In this init function, I initialise a stage with a specific blue background colour, I retrieve the canvas to render to and I use the autoDetectRenderer method to have it automatically select WebGL or Canvas. Then the stage is rendered.
At this point, when loading the page (in Firefox), I expect the grayish canvas to be completely blue, because I’m rendering an empty blue stage. Instead I got a bunch of error messages:
Error: WebGL: Refused to create ANGLE OpenGL context because of blacklisting. pixi.dev.js:5519
Error: WebGL: Refused to create native OpenGL context because of blacklisting. pixi.dev.js:5519
Error: WebGL: WebGL creation failed. pixi.dev.js:5519
Error: WebGL: Refused to create ANGLE OpenGL context because of blacklisting. pixi.dev.js:5519
Error: WebGL: Refused to create native OpenGL context because of blacklisting. pixi.dev.js:5519
Error: WebGL: WebGL creation failed. pixi.dev.js:5519
«Pixi.js v2.2.3 — http://www.pixijs.com/» pixi.dev.js:228
It seems that me, a russian and someone over at kitchenpages were the only people on the whole internet with this issue. And theirs isn’t even pixi related. Thankfully, the kitchenpage post has led me to the solution: Go to about:config and set webgl.force-enabled to true. I’m confused why I am the only other person with this issue…
Anti-aliasing or naw?
After correcting the force-enabled value, the errors disappeared, some new ones appeared but those shouldn’t actually be errors, more like warnings. I mean, I can render without anti-aliasing, right? Right!?
Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. pixi.dev.js:5519
Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. pixi.dev.js:7884
«Pixi.js v2.2.3 — http://www.pixijs.com/» pixi.dev.js:228
Turns out I can’t. Nothing is being rendered. All I see is the gray defined by css. This was all Firefox so far as Chrome doesn’t say anything about it. It’s only the gray square of doom and no output at all.
So, as you may have guessed, this is my first time using pixi.js or, for that matter, any graphical javascript library. I have no idea what I’m doing wrong nor do I know where to look to figure it out. I’ve been to several pixi.js demo pages and all of the apps run perfectly fine. I’m sitting here and can’t even get an empty stage to render and it’s driving me insane.
Please help me understand what’s going on and why any of this is happening.
tl;dr
- WebGL in my script only works when setting about:config webgl.force-enable to true, yet all demos work with it set to false. Why?
- Nothing is being rendered. Why?
- Am I stupid?
Thanks for your replies.
Closed
Bug 1465516
Opened 5 years ago
Closed 5 years ago
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: andy, Assigned: stransky)
Details
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180525140700
Steps to reproduce:
I upgraded to Firefox 60 through my package manager.
At the same time the kernel got upgraded:
```
Transaktion ausgeführt mit:
Installiert dnf-2.7.5-12.fc28.noarch @fedora
Installiert rpm-4.14.1-9.fc28.x86_64 @updates
Veränderte Pakete:
Aktualisiert firefox-60.0.1-1.fc28.x86_64 @updates
Aktualisieren 60.0.1-3.fc28.x86_64 @updates
Aktualisiert glib2-2.56.1-2.fc28.i686 @updates
Aktualisiert glib2-2.56.1-2.fc28.x86_64 @updates
Aktualisieren 2.56.1-3.fc28.i686 @updates
Aktualisieren 2.56.1-3.fc28.x86_64 @updates
Aktualisiert glib2-devel-2.56.1-2.fc28.x86_64 @updates
Aktualisieren 2.56.1-3.fc28.x86_64 @updates
Löschen kernel-4.16.8-300.fc28.x86_64 @updates
Installieren kernel-4.16.12-300.fc28.x86_64 @updates
Löschen kernel-core-4.16.8-300.fc28.x86_64 @updates
Installieren kernel-core-4.16.12-300.fc28.x86_64 @updates
Löschen kernel-devel-4.16.8-300.fc28.x86_64 @updates
Installieren kernel-devel-4.16.12-300.fc28.x86_64 @updates
Aktualisiert kernel-headers-4.16.11-300.fc28.x86_64 @updates
Aktualisieren 4.16.12-300.fc28.x86_64 @updates
Löschen kernel-modules-4.16.8-300.fc28.x86_64 @updates
Installieren kernel-modules-4.16.12-300.fc28.x86_64 @updates
Löschen kmod-acpi_call-4.16.8-300.fc28.x86_64-1.1.1-3.fc28.x86_64 @@commandline
Löschen kmod-tp_smapi-4.16.8-300.fc28.x86_64-0.42-6.fc28.x86_64 @@commandline
Aktualisiert vim-minimal-2:8.1.020-1.fc28.x86_64 @updates
Aktualisieren 2:8.1.026-1.fc28.x86_64 @updates
```
Actual results:
After rebooting I tried to use the Figma App in Firefox that I work with every day, but it told me WebGL was disabled.
https://get.webgl.org/ is telling me
> Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.
The console gives me the following:
```
Error: WebGL warning: Disallowing antialiased backbuffers due to blacklisting.
get.webgl.org:193:16
Error: WebGL warning: Refused to create native OpenGL context because of blacklist entry:
get.webgl.org:193:16
Error: WebGL warning: Failed to create WebGL context: WebGL creation failed:
* Refused to create native OpenGL context because of blacklist entry:
* Exhausted GL driver options.
get.webgl.org:193:16
Error: WebGL warning: Disallowing antialiased backbuffers due to blacklisting.
get.webgl.org:197:20
Error: WebGL warning: Refused to create native OpenGL context because of blacklist entry:
get.webgl.org:197:20
Error: WebGL warning: Failed to create WebGL context: WebGL creation failed:
* Refused to create native OpenGL context because of blacklist entry:
* Exhausted GL driver options.
get.webgl.org:197:20
```
The cause seems to be an empty blacklist entry that somehow applies?
In Chrome it works fine, so I can exclude kernel or graphics drivers issues.
Thanks for help!
Expected results:
I guess WebGL should just have worked?
I just tried booting into the old kernel (4.16.11) but it still doesn't work. Maybe that makes sense (;
Confirmed by another person over at Redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1585300
> The same issue for firefox-60.0.1-5.fc28.x86_64 and Lenovo T470s (Intel HD Graphics 620).
>
> WebGL works ok after downgrade to firefox-59.0.2-1.fc28.x86_64 (no other packages changed).
>
> Enabling layers.acceleration.force-enabled DOES NOT help.
>
> Console output for webglreport.com:
> Error: WebGL warning: Disallowing antialiased backbuffers due to blacklisting.
> Error: WebGL warning: Refused to create native OpenGL context because of blacklist entry:
> Error: WebGL warning: Failed to create WebGL context: WebGL creation failed:
> * Refused to create native OpenGL context because of blacklist entry:
> * Exhausted GL driver options.
Looks like Fedora specific issue with the latest FF update.
Assignee: nobody → stransky
Hey Andy, Which download manager are you using? Are using Fedora? If not, which exact OS are you using? Thanks!
Hei Bodea. I'% using Fedora and YUM.
You need to log in
before you can comment on or make changes to this bug.