Oh Noes! This archived report could not be located. bug 586909

RESOLVED INCOMPLETE

Status

()

Toolkit
Crash Reporting
RESOLVED INCOMPLETE
8 years ago
8 years ago

People

(Reporter: Kevin Brosnan, Unassigned)

Tracking

Trunk
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
I've been running Firefox with WinDbg underneath while trying to get a reproducible stacktrace for bug 586909. Many people who have this bug get crash reports that cannot be processed. I have a dump file that WinDbg created that corresponds to crash id e6645120-cdf4-4c81-bf9d-a6de62100819 which has this problem.

http://dl.dropbox.com/u/686313/nanojit--CodeAlloc--alloc-small.dmp
The crash in this dump is in NanoJIT. VirtualAlloc is returning NULL, and the pointer gets dereferenced and you crash. I suspect that since you've already OOMed, that's why we're failing to write a valid dump. The root cause here is probably a memory leak from D2D.
(Reporter)

Comment 2

8 years ago
I might have oom'ed vram but I was no where close to oom in physical ram.
I'm seeing this on windows too, a few times a day.  Seems pretty serious - any way to fix / diagnose it?
I'm 100% positive that this is just fallout from bug 586909. D2D is causing us to run out of usable memory somehow, which makes us unable to even write a minidump. The minidump is zero bytes, which Socorro can't do anything with. The fact that Socorro says "Archived report could not be located" is also a bug, but there's a new release of Socorro right around the corner, and it's already filed.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.