Complete freeze/disappearing of browser window
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: 53aa7b2d-42f3-4a5a-8b9a-c826a8c64a19, Unassigned)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
I use Pop OS 64 bit, completely up to date. This one is a bit hard to reproduce reliably but it does happen daily to me. Its usually closely after i reopen my laptop and thus wake it from hibernation. i then browse reddit for a bit for example, then when i click post on a written reddit comment that browser window becomes almost completely opaque (some elements like the title bar remain). This also sometimes happens when i go fullscreen on youtube.
Actual results:
That specific browser window seems to crash, large parts of the window become completely opaque, while some UI elements remain the same. the webpage i was on completely disappears. Other tabs in the same window can't be switched to, and the entire UI of that window becomes unresponsive. other windows don't seem affected.
Expected results:
The window should not largely disappear from the view,
Reporter | ||
Comment 1•4 years ago
|
||
Comment 2•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•4 years ago
|
||
I see you have OpenGL compositor enabled. From the description it looks like a problem with HW drivers/HW compositing of the screen.
Can you try to switch bask to Basic (set layers.acceleration.force-enabled to false)?
Updated•4 years ago
|
Comment 4•4 years ago
|
||
"windowLayerManagerType": "OpenGL",
"driverVendor": "nvidia/unknown",
Thanks for the report! This is known and the one popular (and almost reproducible) Nvidia bug. It occurs with the old (bug 1506017) and the new (bug 1535716) OpenGL compositor. You are still using the deprecated one. If you want to use the new one, open about:config, set gfx.webrender.all to true and restart Firefox. (It implies gfx.webrender.enabled and layers.acceleration.force-enabled, therefore you don't need to enable these two prefs.)
You can work around this problem by restarting Firefox after waking up from hibernation. This bug does not occur with Intel or AMD.
Another workaround is setting layers.acceleration.force-enabled to false (its default value) as comment 3 suggests - at the price of worse performance because it means software rendering on your CPU.
Description
•