Closed Bug 621563 Opened 14 years ago Closed 13 years ago

Content processes don't send uptime annotations if exception handler is triggered

Categories

(Toolkit :: Crash Reporting, defect)

Product:
Toolkit
Component:
Crash Reporting
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jdm, Unassigned)

Details

We get the annotations if the content process actor dies in a controlled way via ActorDestroy, but not if we trigger the exception handler.  Presumably http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/nsExceptionHandler.cpp#239 is the culprit, but I suspect that there's a good reason it's in there.
Right, because we don't want to use the chrome process's startup time. You'd have to look at what the plugin code does.
This bug was filed under false pretenses.  Every content crash I look at has the correct annotation, so INVALID.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.