blackout when idle Firefox 53

UNCONFIRMED
Unassigned

Status

()

Core
Graphics
P3
normal
UNCONFIRMED
10 months ago
7 months ago

People

(Reporter: Francois, Unassigned)

Tracking

53 Branch
Points:
---

Firefox Tracking Flags

(firefox53 affected, firefox54 ?, firefox55 ?)

Details

(Whiteboard: [gfx-noted])

Attachments

(1 attachment)

(Reporter)

Description

10 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce:

I "worked" in Photoshop, leaving Firefox53 idle for about 30 minutes


Actual results:

All the 8 tabs had a black screen instead of their usual contents


Expected results:

All tabs correctly showing content.
(Reporter)

Comment 1

10 months ago
I haven't seen that bug for about 6 months now. It has reappeared with the last update to Firefox 53.

Updated

10 months ago
Component: Untriaged → Graphics
Product: Firefox → Core
Hi Francois,

Can you please load up Firefox 53 and attach a copy of about:support to this bug report? Also, can you confirm if you get the compositor process (should see 3 firefox.exe processes in Windows Task manager)?
Flags: needinfo?(vertigostardust)
Whiteboard: [gfx-noted]
(Reporter)

Comment 3

10 months ago
Created attachment 8862562 [details]
aboutsupport53.txt

Firefox 53 about:support
Flags: needinfo?(vertigostardust)
(Reporter)

Comment 4

10 months ago
(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #2)
> Hi Francois,
> 
> Can you please load up Firefox 53 and attach a copy of about:support to this
> bug report? Also, can you confirm if you get the compositor process (should
> see 3 firefox.exe processes in Windows Task manager)?

I've attached the requested about:support file. I have only 2 Firefox processes in Task Manager.
Thanks Francois. It's clear to me from that information that you're not getting the compositor process so that can be ruled out. It must be some other factor that's causing this issue to happen. 

I noticed that your driver is a couple years old, maybe check to see if there's a more current version from Intel (drivers provided by Microsoft Windows Update are usually not current).

If the issue is easily reproducible in Firefox 53 then perhaps you could try running on a new profile with no addons installed and no modifications. This would help rule out changes made to your profile as potential causes.

Another thing you could try is disabling multi-process Firefox to see if the content process is a factor. Do you get the content process in Firefox 52? If not this could be the difference, in which case this would be an e10s bug.
Milan, aside from compositor process, were there any changes to Graphics in Firefox 53 which might result in something like this occurring?
Flags: needinfo?(milan)
(Reporter)

Comment 7

10 months ago
(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #5)
> Thanks Francois. It's clear to me from that information that you're not
> getting the compositor process so that can be ruled out. It must be some
> other factor that's causing this issue to happen. 
> 
> I noticed that your driver is a couple years old, maybe check to see if
> there's a more current version from Intel (drivers provided by Microsoft
> Windows Update are usually not current).
> 
> If the issue is easily reproducible in Firefox 53 then perhaps you could try
> running on a new profile with no addons installed and no modifications. This
> would help rule out changes made to your profile as potential causes.
> 
> Another thing you could try is disabling multi-process Firefox to see if the
> content process is a factor. Do you get the content process in Firefox 52?
> If not this could be the difference, in which case this would be an e10s bug.

The version that triggered the black out was Firefox 53 x86 which my wife got as a routine update
The about:support file is from the Firefox 53 x64 I installed with the suggested link of Firefox 52 in the ? menu

Not wishing to "commandeer" her work laptop, I'll simply reinstall the Firefox 52 x64 version.

Thank you for your help.
I can track this for 53 but not sure we are making any progress here. Milan, is there anyone actively investigating this and bug 1163440?
status-firefox53: --- → affected
status-firefox54: --- → ?
status-firefox55: --- → ?
Flags: needinfo?(milan)
Not really actionable at this point; Nvidia has seen this on their end as well, but we're collectively stuck.  The anecdotal connection to Windows Creators Update (1703) is an interesting piece of information, but I'm not sure what to do with it.
Flags: needinfo?(milan)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.