Closed Bug 945328 Opened 6 years ago Closed 6 years ago

Firefox 25.0.1 Crash Report [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ], WinDbg logs

Categories

(Firefox :: Untriaged, defect)

25 Branch
x86
Windows 7
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tjsepka, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018

Steps to reproduce:

Previously reported in bug 933453.  Disabled each extension one by one and confirmed crash was still happening with all extensions disabled.

Ran FF in WinDbg with all extensions still disabled (same state as caused this crash).

Captured crash in WinDbg (log file is attached).

This crash happens on 3 different machines, all with separate user profiles.


Actual results:

WinDbg log file is attached.
Another WinDbg file (firefox-debug_2790_2013-12-03_12-03-17-700.log) with HWA off this time.  High CPU usage, used up almost all available memory, and hit a WinDbg breakpoint.
Crash Signature: Firefox 25.0.1 Crash Report [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ]
Summary: Firefox 25.0.1 Crash Report [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ] → Firefox 25.0.1 Crash Report [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ], WinDbg logs
Blocks: 933453
Crash Signature: Firefox 25.0.1 Crash Report [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ] → [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ]
Keywords: crash
tjsepka, do you continue to see crashes on 26? If so, could you paste a few of your recent report IDs from about:crashes?

Your windbg logs indicate that you are hitting out-of-memory errors. FF26 has better crash reporting in low-memory situations, so we might be able to get a better understanding of what's going on.
Flags: needinfo?(tjsepka)
I will try to recreate the problem and post any results, either positive or negative.
Flags: needinfo?(tjsepka)
I've rerun the scenarios that caused the out-of-memory errors and they no longer appear to occur in FF26.
(In reply to tjsepka from comment #5)
> I've rerun the scenarios that caused the out-of-memory errors and they no
> longer appear to occur in FF26.

Cool. Thanks for sending the debugger logs. I'll go ahead and resolve this, please reopen if the issue comes back.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.