656924 - Browser crashes upon tab closing after sleep mode, error sending crash report

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[ithildyn]

User-Agent:       Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

It happens on semi-regular basis. Haven't tried to nail exact reproducibility method but will try to be as informative as can be.

Usually, Firefox is open in multiple windows (3), each having a lot of tabs open (about 15+ per window). Usually among the lot there are a few tabbed pages that have scripts running (hotmail, twitter, bandcamp, youtube...)  
Put the computer in low-power/sleep mode for the night. Resumed work in the morning, application is sluggish. Close unnecessary tabs in one window. Browser has long response time, but should improve upon closing down more tabs.

- Often will receive prompts about processes that stopped responding (often coming from hotmail's tab and the such, but sometimes from browser add-ons too). Stopping or letting them run usually works either way. -

Change to another window, proceed to close more tabs judged superfluous. Browser crashes. Mozilla crash reporter comes up, press button to send crash report. Receive message that there was an error in sending the crash report.


Reproducible: Sometimes

Steps to Reproduce:
1.Open high amount of tabs, separated in different Firefox windows.
2.Computer go to sleep/power save mode, let sit few hours.
3.Awaken computer, if Firefox is sluggish, start closing tabs from window to window.

Actual Results:  
Browser crashes. Crash reporter gives error message when submitting report.

Expected Results:  
1.Tabs successfully close. Firefox regains some speed, hurray!
OR
2.Browser still crashes under the load but crash reporter sends report successfully. 

Expected crash reporter might fail, had copied the detail log. Can provide if needed.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

You can try to re-send the Reports if you open "about:crashes" and click onthe Crash Entries without leading "bp-".
You might want to temporary disable Security related Applications before doing that.

Else you could try to run Firefox under WinDbg for a while and catch the Crash under it.
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

Comment 2

[ithildyn]

(In reply to comment #1)
> You can try to re-send the Reports if you open "about:crashes" and click
> onthe Crash Entries without leading "bp-".
> You might want to temporary disable Security related Applications before
> doing that.
> 
> Else you could try to run Firefox under WinDbg for a while and catch the
> Crash under it.
> https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

The about:crashes pages displays the "No crash reports have been submitted" message. :(

Thank you for the WinDbg link.

Comment 3

[Tim (fmdeveloper)]

Reporter -> Are you still experiencing this issue? Have you been able to get a stacktrace?

Comment 4

[Tim (fmdeveloper)]

Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question