Open
Bug 1259133
Opened 9 years ago
Updated 2 years ago
Firefox 45 shows session restore screen on every start
Categories
(Firefox :: Session Restore, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: tantrido, Unassigned, NeedInfo)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160315153207
Steps to reproduce:
Firefox 45 shows session restore screen on every start even with correct exit, restart, etc
Any: turn off computer, or Menu File->Exit. Bug exists in both: Linux and Windows.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Same issue here for quite a while, on three different computers running Windows 7 SP1 x64.
As Aleksey reported, any way of closing Firefox *can* trigger the behavior on restart, but it doesn't happen 100% of the time for me, rather 75%.
I keep 50+ Tabs open, which might be a contributing factor.
Bug seems fixed in Windows. Still exist in Linux, Firefox 47, reproducible in:
- openSUSE 42.1, DE: KDE
- Linux Mint 18, DE: MATE
Happen in 100% cases on session logout/PC restart/Shut down. Works fine on normal exit.
Comment 6•9 years ago
|
||
Very strange. I don't think I've ever seen this reported before.
Would you say this is a regression, starting around the time you reported 2016-03-23?
And if so, can you get a regression range?
Flags: needinfo?(tantrido)
Found the way to reproduce in 100%:
- Open 2 FF windows with many tabs in each
- Exit current OS session
- Next time you'll see session restore screen (probably OS can't close FF with 2 windows properly - kills whole process or something like this).
If I leave only single window with many tabs opened, then next time FF opens properly and restores all the tabs correctly.
| Reporter | ||
Comment 10•9 years ago
|
||
Now reproducible in FF 49 even with single window.
| Reporter | ||
Comment 11•9 years ago
|
||
Reproducible in Linux Mint 18 MATE desktop as well, FF 50.
Comment 12•3 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
Comment 13•2 years ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(dao+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•