1410809 - Hardware Acceleration Leads To Incorrect Rendering of Webpages and UI

Status: RESOLVED INACTIVE

(Core :: Graphics, defect, P2)

Description

[mp6]

Attachment: Screenshot of the Issue

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

Steps to reproduce:

I was using Firefox Nightly as my daily driver, with the latest release (Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 ID:20171022220103) with activated hardware acceleration and Stylo on my 2011 MacBook Pro, surfing on various websites.


Actual results:

First, when a site after the error begins appearing is opened, the rendering is good for a second, then it's changed to the unreadable random-looking layout I screenshotted below.
Also the tab titles and other parts of the UI are unreadable, but not the menu bar.


Expected results:

The text should have been rendered correctly.

Comment 1

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

What does the graphics section of about:support look like?  How often and quickly does this happen?  If it happens right away, running mozregression would be really beneficial if this started happening recently.

Comment 2

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

Perhaps related to RDL landing?

Comment 3

[Revertron]

I have this kind of problems too on 58.0a1, but only on pages and bigger unpainted blocks.

I'm using Windows 7 x64.
It started about 5-7 days ago.
The worst problems I'm seeing are when I restart Firefox with some tabs openned, and FF is openning them again. Current page is rendered normally, but all other pages are rendered with big blocks cut out.

Comment 4

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

Is this easily reproducible for you?  If you can reproduce this without having to spend too much time on a page, it would be amazing if you could run the mozregression tool (http://mozilla.github.io/mozregression/quickstart.html) to help us find out when exactly it started.
The Firefox restart issue may very well be bug 1404422

Comment 5

[Jeff Muizelaar [:jrmuizel]]

Re-open if you still see?