Closed Bug 1285632 Opened 10 years ago Closed 10 years ago

Intermittent dom/plugins/test/mochitest/test_hangui.xul | application crashed [@ Interpret]

Categories

(Core Graveyard :: Plug-ins, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Philor, I'm not sure how to read this log. The application exited with "code 1" which seems unusual for a crash. Is this normal? Also the crash log says that this is an EXCEPTION_BREAKPOINT, which could be an assertion failure, but that would normally print something to the console. EXCEPTION_BREAKPOINT also sometimes is used with hangs, but there is no other evidence of a hang here (and no plugin minidumps). Help?
Flags: needinfo?(philringnalda)
All you get when you needinfo me is gut reactions based on seeing a lot of logs, and understanding virtually none of them. My gut says it's just another Windows plugin hang, of the sort we've been utterly ignoring for months now, coupled with the way that at least on Windows our e10s testing (or just our e10s, dunno) eats hangs, thus the number of bugs I've filed with the summary including "330 seconds without output misreported as CrashingThread."
Flags: needinfo?(philringnalda)
Priority: -- → P4
The logs don't have enough data to do anything with this, so I'm going to close it.
Status: NEW → RESOLVED
Closed: 10 years ago
Priority: P4 → P5
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.