458213 - Firefox 3.0.3 crashes randomly, with no crash reporter and no dump file

Status: RESOLVED INCOMPLETE

(Core :: SQLite and Embedded Database Bindings, defect)

Description

[Tony Marini]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I upgraded to Firefox (FF) 3.0.3 from 3.0.1 on 9/28/08. Since the upgrade, FF has been randomly crashing when accessing various random url's. An example is "http://www.bostonherald.com". Upon crashing, an error message window pops up, sometimes, and states: "Firefox had a problem and crashed. We'll try to restore your tabs and windows when it restarts. Unfortunately the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file."
I have removed all add-ons, plug-ins and themes (except for default) and the same behavior occurs.
I removed FF 3.0.3 completely from my system and re-installed FF 3.0. FF3.0, which had not exhibited crash behavior in the past, now crashes in the same manner as FF 3.0.3.
Additionally, no other software was added or updated on my system other than FF.

Prior to upgrade to FF 3.0.3, I had never experienced a FF crash!

Reproducible: Always

Steps to Reproduce:
1.Start Firefox 3.0.3 via the desktop icon.
2.Type url "http://www.bostonherald.com" or select from history list.
3.
Actual Results:  
Firefox 3.0.3 crashes. Mozilla crash reporter error message (as stated in Details, above, is displayed on Windows desktop.

Expected Results:  
Expected Boston Herald (www.bostonherald.com) website to display in browser window.

I reviewed the bug list and the bug I'm encountering bug # 458042.

Comment 1

[Matthias Versen [:Matti]]

read http://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report and scrol down to the alternative way to generate a stack trace with Windbg

Comment 2

[Tony Marini]

Attachment: useless

Per the request in the e-mail, attached please find a Windbg stacktrace file.

Comment 3

[timeless]

Comment on attachment 341513 [details]
useless

you need to debug child processes

Comment 4

[Tony Marini]

Sorry about the Windbg stack trace file! I'm a HARDWARE engineer/physicist, not a software guy...so please have some pity on me!

The tutorial for the Windbg stacktrace file generation is almost USELESS. Is there a better source/tutorial for getting the information that I need to send to you folks? I spent quite a few hours, and it looks like I came up empty.

Any help/advice/scornful comments are greatly appreciated!!

Comment 5

[Matthias Versen [:Matti]]

The documentation should be enough, you just forgot to select debug child processes as explained in the documentation. Just follow the documentation step by step

Comment 6

[Tony Marini]

Attachment: Stack trace for bug 458213

This should be a valid stack trace...child processes check box was checked!!

Comment 7

[timeless]

closer, could you possibly follow all of the instructions? you didn't include a !analyze command after the crash

Comment 8

[Tony Marini]

Attachment: Correct stack trace for bug 458213

Sorry it took so long to get this...I was sick and there was a death in the family! Bummer month...

Also, nowhere in the documentation does it say to use the !analyze -v command to complete the stacktrace acquisition!

Comment 9

[Shawn Wilsher :sdwilsh]

That still doesn't have the right symbols, which makes it impossible to see where we are crashing.

Comment 10

[Shawn Wilsher :sdwilsh]

This is incomplete until we can get more information.

Comment 11

[Robert Reeves]

Firefox 3.6.24 crashes without crash dump in Windows 2000. Apparently random (e.g. leave computer on a web page for 2 to 3 hours, return to find firefox crashed).

Comment 12

[Matthias Versen [:Matti]]

Robert: This bug is closed and nobody is reading it.
Win2k needs an additional .dll (DbgHelp.dll)  if you want the crash reporter working.
Please create a new bug report and but be sure that you have tested in the Firefox safemode first. Either add a crash ID or a windbg stack trace in your report.

https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report