Closed
Bug 1392563
Opened 8 years ago
Closed 7 years ago
After waking up from suspend, often all tabs that were open are broken and just show spinners
Categories
(Core :: DOM: Content Processes, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u580221, Unassigned)
References
Details
Attachments
(1 file)
1.46 MB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170815141045
Steps to reproduce:
After waking up from suspend, often all tabs that were open are broken and just show spinners.
1. Open a couple of websites
2. Suspend laptop for a while
3. Wake up laptop
Actual results:
All tabs show spinners (see screenshot). When that happens, nothing can be done to fix them including CTRL+SHIFT+R. However I can open new tabs and they work just fine, and if I just close all the broken ones I can resume as if never was anything broken. This never happened before and it seems to be some recent regression.
Expected results:
All tabs work fine after restore from suspend
Updated•8 years ago
|
Component: Untriaged → Layout
Product: Firefox → Core
Updated•8 years ago
|
Priority: -- → P3
Updated•8 years ago
|
Comment 1•8 years ago
|
||
Putting this one in "DOM: Content Processes" for now since the symptoms indicate that we're not doing any Layout for the affected tabs. BTW, I can't reproduce this hang after waking issue on my Linux box.
![]() |
||
Comment 2•8 years ago
|
||
How often do you see this? Also, please provide information on your setup: operating system and desktop shell.
Flags: needinfo?(jonas)
I did see this every 2nd day on GNU/Linux Fedora 26 x64 with gnome-shell / GNOME 3 and Intel Skylake onboard graphics. However, now that you ask I have been on the Fedora 27 beta for 1-2 weeks already and I can't remember seeing it again. Maybe it was some GPU driver issue that has been fixed?
Flags: needinfo?(jonas)
![]() |
||
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Since I haven't seen this in ages, has anyone else ever encountered this? Otherwise, I think it's probably best if I close this issue. As written above, I haven't ever seen it again, so whatever it was (GPU driver bug, firefox bug, ...) it appears that it was fixed.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•