User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20101203 Firefox/3.6.13 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20101203 Firefox/3.6.13 i have been working with more than 20 tabs opened and in google i have searched for one document which was there in search result and when i clicked the link for document the new tab opened and firefox crashed. in the cras report window i selected the restore firefox option as there were many tabs which were important. but the firefox kept crashing every time i restore it and i did not have a chance to read info in my other tabs. Reproducible: Couldn't Reproduce Actual Results: refer details Expected Results: refer details refer details
If you remember the link which you clicked which resulted in the crash, uncheck the tab with that url the next time the Restore Session appears. That should allow you to restart without crashing. Please copy down the url if you can and enter it here so we can investigate. If you can't remember the exact url, you can unselect the other unimportant tabs one at a time to see if you can start without crashing.
This does not appear to be security sensitive, so unmarking.
> but the firefox kept crashing every time i restore it and i did not have > a chance to read info in my other tabs. After a couple of immediate crashes it should come up with a screen showing your list of open windows and tabs, rather than continually opening one that's crashing. Is it crashing before it gets that far? Is it going ahead and trying to open several tabs anyway without asking? possibilities: a) content in one tab is crashing you. If you get the session restore screen uncheck the most recent one you opened and see if that's where the crash is. b) you've got some conflicting software installed on your machine, that somehow got added while you were in your last working session (the one before the first crash). Did you install or update anything? If so that would be my first suspect. If not maybe you have malware? running in "safe mode" might help, if the conflict is in an add-on. Search on http://support.mozilla.com/ for how to do that on your platform. There are also forums there for tech support and they probably know a lot more about real-world problems and conflicts than the focused testers and programmers who look at these bug reports. If you ever do get firefox running again (for example, if safe-mode works) enter "about:crashes" without quotes in the location bar and hit enter. That should bring up a list of the crashes you've submitted to us. Please copy the ID number(s) for the crashes associated with this instance and paste them into the bug. Don't paste earlier crashes, those are just as likely a different problem and will only confuse people looking at this bug.
pavan, could you please update to a recent and supported version (see http://www.firefox.com/ ), create a new profile (see http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile and http://support.mozilla.org/kb/Managing%20profiles for more information), and test this again? If you still see this problem in the new profile, please add a comment to this report and tell us your exact version (by updating the "Version" field of this bug report) and your operating system (Windows, Mac OS, Linux, etc.) and provide a concrete testcase (attachment here, or a link to a page where this problem can be seen). If the problem still happens but does not happen in the new profile, please enter the address "about:support" in the address bar and attach (using the "Add an attachment" link above) the output for your original profile (not the new profile), as the "Modified Preferences" section could be interesting. If the problem does not happen anymore at all, please set the status of this report to RESOLVED > WORKSFORME. Thanks for your help!
Closing based on last comment and lack of response to request for more info.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.