User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729) Summary about says it all, have had these two issues happen a couple times now. Wish I could give the Reproducible: Always Steps to Reproduce: 1. Experience unexpected crash that causes Firefox to exit 2. Install Winamp toolbar (or another 3rd party app) Actual Results: Firefox crashes and/or restarts, session tabs are lost. Expected Results: Firefox to not crash and/or my session tabs to be restored. When Firefox restarts, the "You’re now running Firefox 3.0.13." post-update page is displayed.
I meant to say "I wish I could give the website it crashed on, but it doesn't appear to be in my browsing history".
(In reply to comment #0) > Steps to Reproduce: > 1. Experience unexpected crash that causes Firefox to exit > 2. Install Winamp toolbar (or another 3rd party app) With these steps to reproduce, I'd actually expect Firefox to crash (per step 1). Then again, I don't see how installing a 3rd party app _after_ the crash could change anything about this... Anyway, if you can indeed "always" reproduce this issue, could you please see whether it also happens if you run Firefox in Safe Mode before it crashes and after you restart it, in order to rule out an extension incompatibility? Thanks.
BUILD: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) ADD-ONS: Winamp Toolbar 18.104.22.168 I tried to reproduce this with the Winamp Toolbar (which is an experimental Add-on by the way). While I do not see the crash, the Add-on does lock up Firefox when I try to go to Options. You can see many other people having issues with this add-on: https://addons.mozilla.org/en-US/firefox/reviews/display/12174 I was forced to kill Firefox and restart it. When I did, the session was restored. Based on this, and the lack of feedback from Dave, I'm resolving this as INVALID. I suspect it's probably an issue with the Add-on. Reporter, please reopen if you can reproduce this with the most recent Firefox release. If you can, please provide better details about what add-ons you have installed and the specific steps you follow to reproduce this issue. Thanks.