1603843 - Viewing a CloudApp screen recording does not work in Firefox

Status: VERIFIED FIXED

(Core :: Graphics: CanvasWebGL, defect)

Description

[Botond Ballo [:botond]]

Steps to reproduce

In the latest Firefox nightly, load https://cl.ly/5bfb0a3df1ba.
I tested with mozregression --launch 2019-12-13, to be sure that it's not an addon or other configuration issue.

Expected results

The page loads a video viewer.

Actual results

The page loads blank.

The devtools console displays the following errors:

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. 5bfb0a3df1ba
PixiJS 4.8.2 - WebGL - http://www.pixijs.com/ app.js:33385:24
Error: WebGL warning: linkProgram: Programs with more than 16 samplers are disallowed on Mesa drivers to avoid crashing. app.js:29437:8
TypeError: Argument 1 of WebGLRenderingContext.getProgramParameter is not an object.
app.js:29509:30
Pixi.js Error: Could not initialize shader. app.js:29442:17
gl.VALIDATE_STATUS false app.js:29443:17
gl.getError() 0 app.js:29444:17
Pixi.js Warning: gl.getProgramInfoLog() Programs with more than 16 samplers are disallowed on Mesa drivers to avoid crashing. app.js:29449:21
Error: [$injector:modulerr] Failed to instantiate module viewer due to:
[$injector:nomod] Module 'viewer' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.4.8/$injector/nomod?p0=viewer
i/<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:380
ve/</</<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9978
t@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9451
ve/</<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9763
h/<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:18624
o@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:806
h@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:18473
et@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:20162
s@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7507
ae@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7815
oe@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7063
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:43:28030
u@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:22325
fireWith@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:23137
ready@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:24933
a@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:964
EventListener.handleEvent*J.ready.promise@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:25132
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:25231
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:209
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:214

http://errors.angularjs.org/1.4.8/$injector/modulerr?p0=view…u40ore1n.cloudfront.net%2Fd15afa7e%2Fvendor.js%3A19%3A214%0A vendor.js:9279:11
Loading failed for the <script> with source “https://www.google-analytics.com/gtm/js?id=GTM-K2FZ8RB&cid=1977579554.1576271468”.

Disabling Enhanced Tracking Protection does not resolve the problem.

Comment 1

[Emilio Cobos Álvarez (:emilio)]

It works for me fwiw, but this computer uses the nvidia driver (not mesa) so I think this is just fallout from that linkProgram issue.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

It seems like this is because of bug 777028, so probably given it is that old we should try to either remove the workaround of add some sort of version detection.

Comment 3

[Botond Ballo [:botond]]

Ah, indeed. I overlooked that error and focused in on the second one, leading me to believe it was a content blocking or site issue.

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Does gfx.work-around-driver-bugs=false fix it for you?

Comment 5

[Botond Ballo [:botond]]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)

Does gfx.work-around-driver-bugs=false fix it for you?

It does indeed!

Comment 6

[Emilio Cobos Álvarez (:emilio)]

Attachment: Bug 1603843 - Remove work-around for 7+-year-old Mesa bug. r=jgilbert

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b5ffe1a199b5
Remove work-around for 7+-year-old Mesa bug. r=jgilbert

Comment 8

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/b5ffe1a199b5

Comment 10

[Cristian Fogel [:cfogel]]

Managed to reproduce the issue only on Linux - Ubuntu 19.04 distribution with 73.0a1(2019-12-13). For machines with Windows(10)/macOS(10.15) the loading appeared in order.
Verified with 73.0b12 and 74.0a1(20200203085242) on Ubuntu 19.04.