1448941 - First window missing background and misc components

Status: VERIFIED DUPLICATE of bug 1446553

(Core :: Graphics: WebRender, defect)

Description

[James Gilliland]

Attachment: Selection_102.jpg

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36

Steps to reproduce:

Start Firefox Nightly


Actual results:

Window is missing background color/images on browser chrome and webpages are missing almost all background color and images. Basically its almost all grey everywhere though gradients do seem to have a better chance of being rendered.


Expected results:

Browser looks normal.

Comment 1

[James Gilliland]

Some system details that might be helpful and didn't fit in the reporting fields:
Tested today on nightly 61.0a1 build 20180326132207
Linux 4.13.0-37-generic (ubuntu 17.10)
WM: Gnome Shell
WebGL 1 Driver Renderer	NVIDIA Corporation -- Quadro K1100M/PCIe/SSE2
WebGL 1 Driver Version	4.5.0 NVIDIA 384.111

Comment 2

[James Gilliland]

Attachment: Main github page

Another screenshot of a more complicated page to show how weird its rendering.

Comment 3

[Pascal Chevrel:pascalc]

Hi james, is it a regression or it never worked? Did you try with a new profile?

Comment 4

[James Gilliland]

Started about a week ago I think? I waited a while before posting since most bugs like this get resolved quickly and I'd seen some other rendering bugs being fixed. None of them affected this so I opened a new one.

Yes. I first tried disabling webrender since I'd enabled that but it didn't help. Still concerned it was a profile setting I created a new profile and it did not fix it.

Comment 5

[Darkspirit]

Could you please open about:support, click on the "Copy text to clipboard" button, paste it into a text file and upload it here (Attach File)? Thanks!

Comment 6

[James Gilliland]

Attachment: nightly_support_output.txt

Comment 7

[James Gilliland]

Just got a nightly update and did some testing. It only seems to be happening now with webrender enabled now.

Comment 8

[Darkspirit]

Thanks for checking! :)
According to bug 1401455 comment 78 this may be a duplicate of bug 1446553.

Comment 9

[James Gilliland]

Sounds about right. #1401455 issue was one of the issues I saw getting fixed and held of posting this.

I'll follow there. Thanks!

Comment 10

[Kartikaya Gupta (email:[e-mail])]

Can you try setting browser.startup.blankWindow to false in about:config and restart the browser to see if it still happens? This might be a regression from bug 1447719.

Comment 11

[James Gilliland]

It does not happen with browser.startup.blankWindow=false. I'm not sure if that means this needs to be reopened or if its still a duplicate but it definitely seems to be connected to the bug.

Comment 12

[Kartikaya Gupta (email:[e-mail])]

Thanks for confirming! That mean it's a duplicate, because the issue in bug 1447719 is also due to browser.startup.blankWindow being true. So let's leave this bug as-is and follow along on that one.