Closed Bug 1331518 Opened 8 years ago Closed 8 years ago

Firefox loses tabs when closing Firefox from recent applications

Categories

(Firefox for Android Graveyard :: General, defect)

50 Branch
All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1356563

People

(Reporter: thingy02, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20161208153507 Steps to reproduce: 1. Open Firefox 2. Firefox tries loading a tab, and gets stuck with the progress bar stuck at about 25%. This happens with any tabs you have in Firefox. 3. Close Firefox from the recent applications menu after waiting for over a minute 4. Re-open Firefox only to find all your open tabs are now gone (even with the keep tabs setting turned on). This only seems to happen when Firefox gets stuck when trying to load a tab, and that seems to happen randomly. It's definitely frustrating having all your open tabs closed on you, and they don't appear in the recently closed tabs list in History either. Actual results: All tabs are now gone Expected results: All my tabs should still be there
OS: Unspecified → Android
Hardware: Unspecified → ARM
(In reply to Robotnik from comment #0) > This happens with any tabs you have in Firefox. The answer is probably yes, but just to make sure, even new tabs other than those that were automatically opened on startup? Is this reproducible on Firefox 51 (currently on Beta, will probably be released next week) or Nightly as well (meaning both the startup hangs and the fact that tabs are getting lost in that case)? If you can use ADB [1], a logcat of such a failed startup attempt (plus eventually the subsequent restart) would be most helpful. Please turn on "browser.sessionstore.debug_logging" from about:config as well before recording the logs (needs a browser restart to become effective). [1] If you don't have it, it's available from here: https://developer.android.com/studio/releases/platform-tools.html If I haven't got it wrong, on Windows running "adb logcat -v threadtime | findstr Gecko > firefox.log" from a command line should get you the desired log file.
Flags: needinfo?(thingy02)
Hardware: ARM → All
>even new tabs other than those that were automatically opened on startup? yep, all tabs are completely wiped have not been able to reproduce it accurately, but its happened at least 4 times in the last few months, and I can tell when its about to happen because it no longer loads tabs. Ill try to get a logcat next time its about to happen, or if I can figure out a way to reproduce it
Thanks very much. Firefox 51 and above will contain the fix for bug 1190627, so hopefully the next time this happens, you'll only loose the last minute or two of your session at most. Nevertheless, that kind of hang (which seems to indicate that the rendering engine somehow gets stuck or otherwise incapacitated) is worth its own bug anyway.
Jan should we dupe this to bug 1190627?
Flags: needinfo?(jh+bugzilla)
In theory yes, but since that bug is so hard to reproduce, I'd still like to get some confirmation that this actually works as expected. So I'd still wait a bit before marking this as a dupe. Then there's also the matter of these startup hangs...
Flags: needinfo?(jh+bugzilla)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(thingy02)
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.