I experience rendering issues with FF Developer edition




3 years ago
a year ago


(Reporter: michael.star.mail, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [specification][type:bug][gfx-noted])


(2 attachments)



3 years ago
What did you do?
1. Open a page
2. Open another window (hardware accelerated WPF) that overlap Firefox window
3. Minimize that window and see rendering artifacts.

What happened?
The page was rendered with artifacts (black areas)

What should have happened?
The page had to be rendered normally

Is there anything else we should know?
I'm on the alpha channel but I experience this bug several versions already. 
I have a switchable graphics (Nvidia and Intel).
I have a screenshots.
OS is Windows 10 Pro

Comment 1

3 years ago
Created attachment 8760671 [details]
firefox bug.png

The areas in red is my edits (removed personal info)


3 years ago
Component: General → Graphics
Product: Mozilla Developer Network → Core
Thank you for the report. Does this still occur if you disable acceleration in firefox?

Although you have experienced this for a few releases, as it may still be a regression would you be able to run mozregression to find the regression range? https://mozilla.github.io/mozregression/
Whiteboard: [specification][type:bug] → [specification][type:bug][gfx-noted]

Comment 3

3 years ago
I too experience this on two separate computers (one with switchable graphics, one without). Disabling hardware acceleration does not seem to fix the problem for me. 

Things of note:
- It can go for long periods without occuring
- When it does occur, it is often on a page load
- Mouse movement, page scrolling, tab switching, etc can make it appear/disappear

Windows 10 x64
GTX 980Ti (Computer 1) and GTX 960M + HD530 (Computer 2)

Comment 4

3 years ago
Created attachment 8767449 [details]
rendering bug firefox

Another example image of the bug occurring.

Comment 5

3 years ago
The bug doesn't reproduce after I have switched off hardware acceleration.
You need to log in before you can comment on or make changes to this bug.