1448420 - Hardware Acceleration stopped working

Status: RESOLVED DUPLICATE of bug 1458553

(Core :: Security: Process Sandboxing, defect, P3)

Description

[rob terhaar]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180315233128

Steps to reproduce:

Upgraded from Firefox 60 from 59, MacOS 10.13.3


Actual results:

Hardware acceleration stopped working. Unable to use Google Maps.


Expected results:

Expected hardware acceleration to continue working.

Comment 1

[Cristina Badescu [:cbadescu], Experiments QA]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180404171943

Hello Rob,

I have tested this issue on latest Firefox Beta 60.0b10 and could not reproduce it. I have upgraded an older Firefox Beta version 59.0b14 (Build ID: 20180301022608) to the current one and everything worked as expected. I've also managed to use Google Maps without encountering any issue.

Just to be sure, did you encounter this issue after updating from Beta 59 to Beta 60?
Can you please retest and use a new clean Firefox profile (https://goo.gl/AWo6h8), maybe even safe mode (https://goo.gl/AR5o9d), to eliminate custom settings as a possible cause and report back the results?

Thanks.

Comment 2

[rob terhaar]

Thanks for your response.

I have already tried a new profile, but it did not fix the issue.

I just tested again (v60 b11, MacOS 10.13.4), and hardware acceleration has stopped working. My computer is a 2010 Mac Pro, using an Nvidia GTX 680 video card. The problem happens regardless if I use the Nvidia "web driver" or the MacOS driver. Hardware acceleration works fine with this computer using Firefox v59.

I do not have any issues on my MacBook Pro (13-inch, 2017).

Comment 3

[Cristina Badescu [:cbadescu], Experiments QA]

Hello,

If you don't mind, can you please provide in a .txt document the information from the "about:support" page? You can do this by navigating to it, click the "Copy raw data to clipboard" button, copy and paste the information in the document.

Thanks.

Comment 4

[rob terhaar]

Attachment: ff60.json

data from about:support is attached.

Comment 5

[Milan Sreckovic [:milan] (needinfo for best results)]

Can you tell us more about the symptoms?  Hardware acceleration is fine overall, Firefox must have it or it doesn't run.  However, given that you're talking about Google Maps, it's either canvas or webgl that may have a problem (although WebGL is reporting no troubles.)

Could you go to about:config and toggle layers.omtp.enabled to false, restart and let us know if it's still broken?

If that doesn't help, could you (also in about:config), set gfx.canvas.azure.accelerated to false, restart, and see if that helps?

Comment 6

[Milan Sreckovic [:milan] (needinfo for best results)]

(In reply to Milan Sreckovic [:milan] (needinfo for best results) from comment #5)
> Can you tell us more about the symptoms?  Hardware acceleration is fine
> overall, Firefox must have it or it doesn't run.

Sorry, looking at Android bugs today, and this is Mac, so things got mixed up.  Of course things work without acceleration on the Mac.

Still the same question though - "acceleration not working" looks like what on your machine?

Comment 7

[rob terhaar]

Here's a video I made showing the problem (captured with layers.omtp.enabled=true, gfx.canvas.azure.accelerated=true)
https://www.dropbox.com/s/6kl10v6msiykr43/firefox.mov?dl=0
Maps is working fine in 59.0.2, but starting in v60 (or in this case 61b2) it's not working anymore.

Setting layers.omtp.enabled to false (and restarting) made it a tiny bit more responsive, but it did not fix the problem.

Setting gfx.canvas.azure.accelerated to false (and restarting) made no difference, still not working.

Comment 8

[Milan Sreckovic [:milan] (needinfo for best results)]

Thanks for the video, that is a serious issue.  Any chance of running mozregression (https://mozilla.github.io/mozregression/quickstart.html) to find out exactly this stopped working?  It would help us find out what's going on.

Comment 9

[rob terhaar]

Mozregression is very cool!

Here are the results:

20:17.08 INFO: Narrowed inbound regression window from [ba8db0fb, db5209b5] (3 builds) to [ba8db0fb, 6b101438] (2 builds) (~1 steps left)
20:17.08 INFO: No more inbound revisions, bisection finished.
20:17.08 INFO: Last good revision: ba8db0fbc00605d6d097dde0b7e034297f55c1ec
20:17.08 INFO: First bad revision: 6b101438c684bff925471edbfe593e500bcb3a03
20:17.08 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ba8db0fbc00605d6d097dde0b7e034297f55c1ec&tochange=6b101438c684bff925471edbfe593e500bcb3a03

Comment 10

[rob terhaar]

I tried setting security.sandbox.content.level=2 under about:config (and restarted) and Google Maps still did not scroll correctly for me.

Comment 11

[Cristina Badescu [:cbadescu], Experiments QA]

Haik, can you please take a look at this issue and see what might have caused it?
However, the pushlog is confusing since the reporter cannot reproduce the issue on Firefox 59.0.2 and the fix was targeted in Firefox 56.
Thanks.

Comment 12

[Haik Aftandilian [:haik]]

Rob, thanks for reporting this.

This sounds like a duplicate of bug 1458553 "Return of Google Maps all black map with updated Nvidia web driver on Mac" apart from that you mentioned you experience the problem with/without the Nvidia web driver. The fix for bug 1458553 is in Firefox Beta at the moment and we plan to uplift the fix to build 60. Could you give the current Firefox Beta a try to see if that solves your problem?

Comment 13

[rob terhaar]

Confirmed, 61.0b5 is working for me now.