1681232 - Large blank area at top of page after computer boot

Status: RESOLVED DUPLICATE of bug 1663273

(Core :: Graphics, defect, P3)

Description

[pepaltavista]

Attachment: Firefox bug before.jpg

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Open addons page
Reboot computer

NOTE: This only happens after the computer is booted. A restart of firefox clears the issue, until the next time the computer is booted.

Actual results:

Large blank area at top of page.

Expected results:

Normal page display.

Comment 1

[pepaltavista]

Attachment: firefox about support.txt

Comment 2

[pepaltavista]

This happens on many pages, but I have reported it for the internal addons page to circumvent lost effort investigating 3rd party web pages.
Also, I have disabled all my addons but the problem still persists, so it does not appear to be related to any particular addon.

Comment 3

[Peter Magyari (Desktop QA)]

Hi!

Would you mind checking if this also happens on a freshly created profile ? (you won't lose your old one)
Here is a link that can help you with that: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

Thanks!

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 5

[pepaltavista]

(In reply to Peter_M from comment #3)

Hi!

Would you mind checking if this also happens on a freshly created profile ? (you won't lose your old one)
Here is a link that can help you with that: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

Thanks!

No it does not happen in a new profile.

So I'm guessing this means it has something to do with a setting in my default profile, but if so I have no idea how to find which one is causing it or even how to reset them all back to default.

Comment 6

[Alex Cornestean]

Hello pepaltavista,

As I’ve read in Comment 5, the issue you are having won’t occur when using a new profile. So I’ll create a profile myself and use it for a time to maybe mimic an older one with some usage. Afterwards I’ll attempt to reproduce the issue.

I will post the results here as soon as they are available.

Comment 7

[pepaltavista]

(In reply to Alex Cornestean from comment #6)

Hello pepaltavista,

As I’ve read in Comment 5, the issue you are having won’t occur when using a new profile. So I’ll create a profile myself and use it for a time to maybe mimic an older one with some usage. Afterwards I’ll attempt to reproduce the issue.

I will post the results here as soon as they are available.

Hi Alex,
I've just determined that there is no problem if the computer crashes, which suggests the problem is connected to the browsers shutdown process. Hope that helps you narrow down the cause.

Merry xmas and happy new year.

Comment 8

[Micah [:mtigley] (she/her)]

Hello, we suspect this could be a rendering issue with WebRender. Are you able to reproduce this issue with the pref "gfx.webrender.all" set to false?

You can set this pref by visiting about:config and searching "gfx.webrender.all".

Comment 9

[pepaltavista]

(In reply to Micah Tigley [:mtigley] from comment #8)

Hello, we suspect this could be a rendering issue with WebRender. Are you able to reproduce this issue with the pref "gfx.webrender.all" set to false?

You can set this pref by visiting about:config and searching "gfx.webrender.all".

Unfortunately the bug is still there after turning off webrender.

Comment 10

[Micah [:mtigley] (she/her)]

Emilio, this could be an issue on the layout side. Do you know what might be happening here? Or if you could point us to someone else that might.

Comment 11

[Emilio Cobos Álvarez (:emilio)]

(In reply to pepaltavista from comment #9)

Unfortunately the bug is still there after turning off webrender.

Sorry, the right way to turn of webrender is gfx.webrender.force-disabled. With that flag set to true, do you still see it?

Also, when this bug happens, does switching to another tab and switching bag fix it?

Comment 12

[pepaltavista]

Sorry, the right way to turn of webrender is gfx.webrender.force-disabled. With that flag set to true, do you still see it?
Setting that flag to true had no effect, the bug is still active.
Also, when this bug happens, does switching to another tab and switching bag fix it?
Switching tabs has no effect on the bug.

Comment 13

[Emilio Cobos Álvarez (:emilio)]

Ok, thank you! then this seems more of a Widget / Graphics issue.

It seems you're using KDE+X11, does using Wayland help? You can launch it with MOZ_ENABLE_WAYLAND=1 firefox -no-remote. That could help isolate it.

Comment 14

[Martin Stránský [:stransky] (ni? me)]

It looks like WebRender + proprietary NVIDIA drivers bug. Can you test latest nightly please? Looks like dupe of Bug 1663273.

Comment 15

[pepaltavista]

(In reply to Martin Stránský [:stransky] from comment #14)

It looks like WebRender + proprietary NVIDIA drivers bug. Can you test latest nightly please? Looks like dupe of Bug 1663273.

Can confirm the bug is not in the nightly build.

So while this is really good, I obviously don't want to run nightly for my main browser, so can you give me a estimated timeline when the fix from nightly will be pushed to stable?

Thanks very much for the help guys :)

Comment 16

[Martin Stránský [:stransky] (ni? me)]

(In reply to pepaltavista from comment #15)

(In reply to Martin Stránský [:stransky] from comment #14)

It looks like WebRender + proprietary NVIDIA drivers bug. Can you test latest nightly please? Looks like dupe of Bug 1663273.

Can confirm the bug is not in the nightly build.

So while this is really good, I obviously don't want to run nightly for my main browser, so can you give me a estimated timeline when the fix from nightly will be pushed to stable?

Should be released next Tuesday (2021-01-26) in Firefox 85.

Comment 17

[pepaltavista]

(In reply to Martin Stránský [:stransky] from comment #16)

Should be released next Tuesday (2021-01-26) in Firefox 85.

Thanks, I look forward to it.

Comment 19

[pepaltavista]

Can confirm bug is resolved in v 85.0 which I installed yesterday.
tyvm