I received this amusing Firefox error message when opening Firefox this morning. The strange thing is that Firefox still let me load all my tabs from the previous browsing session, so I’m not sure if there was actually a problem. I upgraded an extension as I was opening, but I’m not sure if it was related.
I’ve been very happy with Firefox 3.5 and enjoying the speed improvements.
Andy D'Silva
I usually get that error when I haven’t used File> Exit. I noticed the error shows when you click on the “X”.
Also, do you have “minimize to tray” running? if you do then this will happen unless you right click and “Exit” firefox from there or as I mentioned above.
Since doing that I haven’t see this error each time I start up firefox.
September 4th, 2009 at 3:42am
digitalpbk
Same thing happend to me after loading my blog , firefox crashed
lol
anyone with the same problem in seeing my blog on firefox ?
Try embarrassing message
December 10th, 2009 at 12:40am
Tony, Newcastle
This was occurring all the time for me. Turned out to be a trojan buried in GoogleUpdate.exe then replicated itself into GoogleUpdateBeta.exe.
Very easy to get rid of, you can search but use msconfig.msc to get rid of googleupdate from startup and services. Then search in regedit for it and delete both keys and locations indicated in reg settings. Then check scheduledtasks in control panel for self inserter buried there. Then Firefox behaves forever.
Only had trouble on one computer because ZoneAlarm catches this on the other.
December 18th, 2009 at 1:15am
vamsi
if we have more than 1 active tabs.this will happen
btw the live comment preview is damn sexy !
February 4th, 2010 at 9:04pm
Vlad
Now don’t quote me on this, but I’m pretty sure that if you hit “Start New Session” by accident, you can click the back button to go back to that error and click “Restore.”
I haven’t had that happen so I can’t confirm now but I remember having that happen before.
April 18th, 2010 at 9:13am
Jason Miller
That message is displayed when Firefox can’t verify that it was closed properly. Since a hard crash prevents the browser from saving your session, it is saved incrementally. If the most recent incremental save hasn’t been “capped” by a proper application quit, it considers that saved session to be a restore point instead of a verified session.
Personally, I think it’s a much more graceful way to handle the error in contrast to other browsers’ features. Now if Firefox would just crash a little less often, any user experience flaws would go virtually unnoticed.
April 21st, 2010 at 12:33pm
Leave a comment