Closed Bug 635846 Opened 13 years ago Closed 13 years ago

When restarting Firefox, I get the "Well, this is embarrassing" message every time I have blank tabs.

Categories

(Firefox :: Session Restore, defect)

3.6 Branch
x86_64
Windows Vista
defect
Not set
minor

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: email, Unassigned)

References

()

Details

User-Agent:       Opera/9.80 (Windows NT 6.0; U; en) Presto/2.7.62 Version/11.01
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

I've set Firefox to remember my tabs on close. If I only have a blank tab open, I receive the "Well, this is embarrassing" message every time I start the browser. If I have more than one blank tab or a blank tab and a non-blank time, I receive this message most of the time, but occasionally not.

Reproducible: Always

Steps to Reproduce:
1. In Tools > Options > General tab, set Firefox to "Show my windows and tabs from last time"
2. Open up a new tab.
3. Close all tabs but the blank tab.
4. Restart Firefox.
Actual Results:  
I receive the "Well, this is embarrassing." message.

Expected Results:  
I should just see a blank tab.

This issue seems to be independent of theme, since the problem persists with themes enabled or disabled. My only extensions are Adblock Plus, Web Developer, and Firebug, fairly popular plugins. I've noticed the bug in both Windows Vista and Windows 7.

As soon as I hit Restore, I am back to a blank tab, or I could also enter a URL in the address bar, so it's a minor inconvenience. It's still a bug, though.
Component: Tabbed Browser → Session Restore
QA Contact: tabbed.browser → session.restore
Please try again with the latest beta version of Firefox 4:
http://www.mozilla.com/en-US/firefox/beta/?WT.mc_id=hp_1&WT.mc_ev=click

If it still happens please disable all add-ons and re-run the test.
Version: unspecified → 3.6 Branch
The update solved most of it. It doesn't display the "Well, this is embarrassing" message anymore, but it does displays my homepage instead of the blank tab. I'm not sure if that's a bug or a feature. I'd rather it displayed the blank tab, but at least there's no error message anymore, so that's good! None of my add-ons were compatible with Opera -- excuse me, I mean Firefox 4 -- so they were all disabled anyway.
The update solved most of it. It doesn't display the "Well, this is embarrassing" message anymore, but it does displays my homepage instead of the blank tab. I'm not sure if that's a bug or a feature. I'd rather it displayed the blank tab, but at least there's no error message anymore, so that's good! None of my add-ons were compatible with Opera -- excuse me, I mean Firefox 4 -- so they were all disabled anyway.
 Mozilla/5.0 (Windows NT 6.1; rv:2.0b12) Gecko/20100101 Firefox/4.0b12

(In reply to comment #3)
> ... but it does displays my homepage instead of the
> blank tab. I'm not sure if that's a bug or a feature. I'd rather it displayed
> the blank tab, but at least there's no error message anymore, so that's good!

Check Preferences|General and look at the setting "When Firefox starts". That could be responsible for opening the homepage.

Setting issue to Resolved WFM. If you run into the problem again, feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
(In reply to comment #3)
> The update solved most of it. It doesn't display the "Well, this is
> embarrassing" message anymore, but it does displays my homepage instead of the
> blank tab. I'm not sure if that's a bug or a feature. I'd rather it displayed
> the blank tab, but at least there's no error message anymore, so that's good!

Also see the lengthy discussion here:
http://groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/1796b7255f23067a#
Status: RESOLVED → VERIFIED
Yes, I suppose that's fair, since FF4 has an alternative implementation. I can't say I like the FF4 approach, but as long as there is an option to automatically restore my session on start, I won't complain. Still, that's another topic, and it looks like that's already being discussed ad nauseum in the thread you linked to, so we can close this one.
You need to log in before you can comment on or make changes to this bug.