Created attachment 543913 [details] Screenshot 1 - Nightly Build id : Mozilla/5.0 (Android;Linux armv7l;rv:6.0a2)Gecko/20110704 Firefox/6.0a2 Fennec/6.0a2 Device: Motorola Droid 2 OS: Android 2.2 Build id : Mozilla/5.0 (Android;Linux armv7l;rv:7.0a1)Gecko/20110704 Firefox/7.0a1 Fennec/7.0a1 Device: Motorola Droid 2 OS: Android 2.2 Steps to reproduce: 1. Open Fennec App 2. Open a new blank tab 3. Close all tabs, except the one opened at step 2 4. Go to Preferences > Langauge 5. Change the Language Pack 6. Tap on Restart button Expected result: After step 6, Fennec restarts normally and for: - Aurora 6: a blank tab is opened - Nightly 7: it will be loaded the selected Start Page Actual result: After step 6, for both Aurora 6 and Nightly 7, Fennec is frozen, except the favicon button (its options doesn't work either). Notes: For Aurora build, if Fennec data is cleared from the system, user will be able to use the app normally. But for Nightly build, if the same operation will be performed, a message is displayed when the app opens: "Your Fennec profile cannot be loaded. It may be missing or inaccessible. [OK]" Please see the following video: http://www.youtube.com/user/qaioana#p/a/u/0/vWnGoyXrle8
Severity: critical → major
Summary: Fennec is frozen if it has been restarted while it was opened only one blank tab → Fennec UI is unresponsive and browser becomes unusable if a restart is triggered with a single blank tab open
I can reproduce this with the current nightly.
Could this be the session restore ending up with no tabs open after restoring the session? If so, I've had a patch for this in my queue for a while (I was running into this by making mistakes editing session restore, rather than restarting)
Just to note, it's only the first hunk of that patch that's relevant to this, you could just apply that and ignore the rest.
I'm able to reproduce this issue on the Beta build from https://bugzilla.mozilla.org/show_bug.cgi?id=676780#c30 It seems that the patch doesn't work for this issue. After the last step, I cannot use the app any more. I have to clear Fennec's Data from the System.
(In reply to Cristian Nicolae (:xti) from comment #7) > I'm able to reproduce this issue on the Beta build from > https://bugzilla.mozilla.org/show_bug.cgi?id=676780#c30 > It seems that the patch doesn't work for this issue. After the last step, I > cannot use the app any more. I have to clear Fennec's Data from the System. It's even worse. If I clear data, every time when I open Fennec I have the same message as is specified in comment #0 ("Your Fennec profile cannot be loaded. It may be missing or inaccessible. [OK]"). So I must uninstall Fennec and reinstall it back to be able to use the app again.
This is fixed on trunk by the m-c patch in bug 676780. I haven't tested it with the beta patch.
Depends on: 676780
Created attachment 552101 [details] [diff] [review] patch for beta This patch fixes the problem in beta.
Attachment #552101 - Flags: review?(mark.finkle) → review+
Comment on attachment 552101 [details] [diff] [review] patch for beta we are taking this and will spin a build for QA to test. land on mozilla-beta
Attachment #552101 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
http://hg.mozilla.org/releases/mozilla-beta/rev/8263a2c99c2a not fixed in trunk yet. that is bug 676780
tracking-fennec: ? → 6+
status-firefox6: --- → fixed
status-firefox7: --- → affected
status-firefox8: --- → affected
Fixed in Aurora (Fx7) and Nightly (Fx8) by bug 676780.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
status-firefox7: affected → fixed
status-firefox8: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 6
Verified Fixed on Beta Mozilla/5.0 (Android; Linux armv7l; rv:6.0) Gecko/20110810 Firefox/6.0 Fennec/6.0 Verified Fixed on Aurora Mozilla/5.0 (Android; Linux armv7l; rv:7.0a2) Gecko/20110812 Firefox/7.0a2 Fennec/7.0a2 Verified Fixed on Nightly Mozilla/5.0 (Android; Linux armv7l; rc:8.0a1) Gecko/20110812 Firefox/8.0a1 Fennec/8.0a1
Status: RESOLVED → VERIFIED
Keywords: verified-aurora, verified-beta
You need to log in before you can comment on or make changes to this bug.