firefox tries to recover the last execution state and just ends up in that failed state
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: jsearle3, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763
Steps to reproduce:
Pulled in:
changeset: 463702:52b03bc34899
tag: tip
user: Jan Varga <jan.varga@gmail.com>
date: Mon Mar 11 15:35:04 2019 +0100
summary: Bug 1534208 - LSNG: DOM File thread and PBackground child for it must be created as soon as possible; r=asuth
and built firefox.
See Bug 1532190 for how it was built and how I run it for details.
Actual results:
Running firefox just ends up in the failed state mentioned in the aforementioned bug.
Expected results:
It has been popping up a window that states that firefox could not recover my last session and ask me what I want to do. I've been selecting start a new session, but now I'm no longer offered this opportunity.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
I am attempting to confirm this bug, but I cannot. Can you help me understand what the problem is here? How can I reproduce it myself so I can confirm it?
Thank you for your contribution!
Reporter | ||
Comment 2•6 years ago
|
||
Well, firefox nightly is quite a moving target as it changes every several hours. Right now the problem listed in Bug 1532190 is still happening on Windows 10. Rerunning firefox under The Community Edition of Visual Studio 2017 after having previously failed to shutdown properly sometimes thinks it has restored the previous state, but other times it throws up a window saying "Sorry. We’re having trouble getting your pages back." and asks you what do you want to do? In this instance I select the "Start New Session" button. When it has restored the previous state, it is not currently immediately crashing. But the session is never completely restored as it does not reload my temporary add-on. Luckily I can now successfully build firefox one Windows 10 after more than a week of turmoil in getting the build process to stabilize on mozilla-central.
Comment 3•6 years ago
|
||
I cannot confirm it since I do not have the necessary technical skills to understand it completely. I will set its component to (Firefox) Session Restore since it is related to it. Hopefully, a developer will have an opinion about how to address it further. Please change the component it to a more appropriate one if this is incorrect. Thanks.
Comment 4•6 years ago
|
||
Bodea, I appreciate the triage, but this behavior is not caused by session restore, but apparently triggered by a crashing build.
I'm marking this bug as invalid instead, because we can't support custom setups like this.
Description
•