Closed
Bug 1392638
Opened 8 years ago
Closed 4 years ago
Firefox/Thunderbird window are black / don't refresh on MultiMon Windows 10 after ScreenSaver when hardware acceleration is enabled
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: igors233, Unassigned)
References
Details
(Whiteboard: [gfx-noted])
Attachments
(1 file)
356.39 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
Steps to reproduce:
- On a two monitor Windows 10 computer with primary monitor being external monitor and secondary monitor being notebook's monitor.
- Open Thunderbird (ver 52.3, latest 32bit release version)
- Move Main Window to primary monitor
- Wait till screensaver is invoked or computer locked
- Return to Windows
Actual results:
Thunderbird main window (and all other opened windows on primary monitor) are completely black.
Moving main window to secondary monitor, main window content becomes visible on secondary monitor but remains black on primary.
To get window to display normal on primary monitor as well, whole window has to be moved to secondary monitor, maximized, restored (normal size), moved back to primary monitor.
Expected results:
Main and all other Thunderbird windows should be shown as before computer went to screenSaver mode.
Yellow line on Screenshot marks border between primary and secondary monitor.
Comment 2•7 years ago
|
||
(In reply to Igor from comment #0)
> Thunderbird main window (and all other opened windows on primary monitor)
> are completely black.
Are you using HWA (hardware acceleration)? Tools > Options, Advanced.
If so, try without it.
The refresh problem you're describing has to do with the graphics drivers you're using. We're unlikely able to address the problem. That said, TB is using Mozilla Core functionality for many things it does, like rendering stuff onto the screen. If the problem can be reproduced in FF, we move the bug to the FF queue.
Thanks for the comments, I've tested beheviour in past few days and if hardware acceleration is disabled in Thunderbird, there's no problem (perhaps it should be disabled by default).
I've also tested Firefox (with hardware optimization on) and it exibits same problem - black screen after screen saver.
Comment 4•7 years ago
|
||
HWA *is* disabled by default in Thunderbird.
I'm moving this to Core::Graphics. I have the same problem on one of my machines, so I have to switch HWA off in both TB and FF.
Component: Untriaged → Graphics
Product: Thunderbird → Core
Summary: Thunderbird windows refreshing on MultiMon Windows 10 after ScreenSaver → Firefox/Thunderbird windows refreshing on MultiMon Windows 10 after ScreenSaver
Updated•7 years ago
|
Blocks: tb-hwa
Summary: Firefox/Thunderbird windows refreshing on MultiMon Windows 10 after ScreenSaver → Firefox/Thunderbird window are black / don't refresh on MultiMon Windows 10 after ScreenSaver when hardware acceleration is enabled
Comment 5•7 years ago
|
||
I cannot reproduce this. Here I have a Windows 10 laptop with a secondary external screen. Regardless of which display I place Thunderbird onto, it all resumes normal operation after screensaver operation. Yes, HWA is enabled.
Comment 6•7 years ago
|
||
Since this depends on hardware and drivers, not everybody can reproduce it. I have one machine where I need to switch HWA off to avoid the described effect, and another with HWA switched on not showing the problem. So "not me" reports don't help, what would be interesting is to collect technical data from the "me too" people. This should be handled by the Mozilla graphics team who have the expertise. The problem also affects Firefox.
(In reply to Chris Ramsden from comment #5)
> I cannot reproduce this. Here I have a Windows 10 laptop with a secondary
> external screen. Regardless of which display I place Thunderbird onto, it
> all resumes normal operation after screensaver operation. Yes, HWA is enabled.
Make sure to:
set screensaver (bubles, for example)
to wait for 1 minute of inactivity
and check - "On resume, display logon screen"
For me, after windows goes to screensaver and lock screen, on return Thunderbird/Firefox window is black (on external, non laptop monitor).
Comment 8•7 years ago
|
||
Jorg: OK, but in replying I am confirming that we are looking at the problem, and hopefully I am providing some data as to how widespread the issue is. If it affects 50% of the user base we need to attend to it. It if affects 1% then maybe the pragmatic answer is to advise to switch off HWA.
I don't see the settings that Igor describes; maybe because this machine is company property and locked down in some way by the IT folk. Perhaps this issue affects only certain types of screensaver? I recall OpenGL-based screensavers being problematic.
(In reply to Chris Ramsden from comment #8)
> I don't see the settings that Igor describes; maybe because this machine is
> company property and locked down in some way by the IT folk. Perhaps this
> issue affects only certain types of screensaver? I recall OpenGL-based
> screensavers being problematic.
In case it helps, it's under Lock screen, Screen Saveer settings, here is snapshot: https://postimg.org/image/grurpmsbp/
I've just tried, it's same with any other screen saver or no screen saver at all (none), it's just needs to get to logon screen.
Also sometimes it doesn't happen if only main Thunderbird window is running but it happens always if additional window is (like write new message).
Comment 10•7 years ago
|
||
On the Windows machine which doesn't recover after the screen saver got activated, I'm using the stock-standard Windows screen saver "Blank" (or "Black"?), screen goes black.
Updated•7 years ago
|
status-firefox55:
--- → affected
status-firefox56:
--- → affected
status-firefox57:
--- → affected
status-firefox-esr52:
--- → affected
Priority: -- → P3
Whiteboard: [gfx-noted]
Reporter | ||
Comment 11•4 years ago
|
||
Update, I'm not seeing this issue anymore.
HWA is enabled and thunderbird windows remains normal after returning from logon screen.
Updated•4 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•