Open Bug 1251786 Opened 8 years ago Updated 2 years ago

Firefox stops rendering correctly, instead renders white header and black page

Categories

(Core :: Graphics, defect, P3)

44 Branch
x86_64
Windows 10
defect

Tracking

()

People

(Reporter: bryce, Unassigned)

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

Attached image Screenshot of Issue
Firefox intermittently stops rending pages correctly, and instead displays a white header and black area instead of the page being viewed (see attached screenshot). I am unable to find steps to reproduce, but I would say the issue happens around once every couple of hours of use.

Points of interest:
- Once this occurs it affects all open tabs and windows as far as I can tell. Switching tabs or windows will result in the same issue. It is not isolated to the specific tab in which is first occurs.
- Opening a new window with control + n fixes the problem across all windows and tabs, which is my current work around for when this happens.
- This is occurring on a bootcamped Windows 10.
Attaching about support from affected browser.
Further note I forgot to include in the initial report: I've tried running with hardware acceleration disabled under Options -> Advanced and this did not seem to have any impact: the issue was still occurring.
I see the following in about:support which suggests something is going wrong:

(#0) Assert: Out of sync D3D11 devices in BeginFrame
(#100) Assert: [D2D1.1] 3CreateBitmap failure Size(64,64) Code: 0x8899000c format 0
(#101) Assert: Failed to create bitmap to make DrawTarget copy. Size: Size(2316,1184) Code: 0x8899000c
(#102) Assert: Failed to create bitmap to make DrawTarget copy. Size: Size(2316,1184) Code: 0x8899000c
(#103) Assert: [D2D1.1] 4CreateBitmap failure Size(66,28) Code: 0x8899000c format 0
(#104) Assert: [D2D1.1] 4CreateBitmap failure Size(48,48) Code: 0x8899000c format 1


(In reply to Bryce Van Dyk (:SingingTree) from comment #2)
> Further note I forgot to include in the initial report: I've tried running
> with hardware acceleration disabled under Options -> Advanced and this did
> not seem to have any impact: the issue was still occurring.

This is pretty surprising, are you certain of it?
Flags: needinfo?(bvandyk)
(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)
> I see the following in about:support which suggests something is going wrong:
> 
> (#0) Assert: Out of sync D3D11 devices in BeginFrame
> (#100) Assert: [D2D1.1] 3CreateBitmap failure Size(64,64) Code: 0x8899000c
> format 0
> (#101) Assert: Failed to create bitmap to make DrawTarget copy. Size:
> Size(2316,1184) Code: 0x8899000c
> (#102) Assert: Failed to create bitmap to make DrawTarget copy. Size:
> Size(2316,1184) Code: 0x8899000c
> (#103) Assert: [D2D1.1] 4CreateBitmap failure Size(66,28) Code: 0x8899000c
> format 0
> (#104) Assert: [D2D1.1] 4CreateBitmap failure Size(48,48) Code: 0x8899000c
> format 1
> 
> 
> (In reply to Bryce Van Dyk (:SingingTree) from comment #2)
> > Further note I forgot to include in the initial report: I've tried running
> > with hardware acceleration disabled under Options -> Advanced and this did
> > not seem to have any impact: the issue was still occurring.
> 
> This is pretty surprising, are you certain of it?

Does a restart need to take place for the setting to take effect? I'm fairly certain I've seen this while said box has been unchecked, but also that a restart did not take place between unchecking the box and the fault. Will disable again and see if I have the issue to confirm.
Flags: needinfo?(bvandyk)
(In reply to Bryce Van Dyk (:SingingTree) from comment #4)

> Does a restart need to take place for the setting to take effect? I'm fairly
> certain I've seen this while said box has been unchecked, but also that a
> restart did not take place between unchecking the box and the fault. Will
> disable again and see if I have the issue to confirm.

Yes. Restarting is required for the setting to take effect.
(In reply to Jeff Muizelaar [:jrmuizel] from comment #5)
> (In reply to Bryce Van Dyk (:SingingTree) from comment #4)
> 
> > Does a restart need to take place for the setting to take effect? I'm fairly
> > certain I've seen this while said box has been unchecked, but also that a
> > restart did not take place between unchecking the box and the fault. Will
> > disable again and see if I have the issue to confirm.
> 
> Yes. Restarting is required for the setting to take effect.

Scratch the above then. I am currently running with acceleration disabled, will update this should the fault occur (though it seems likely that it is indeed a hardware related problem).
Whiteboard: [gfx-noted]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: