Closed Bug 1205289 Opened 9 years ago Closed 8 years ago

Crash @ WaitForSingleObjectEx | je_isqalloc | PR_WaitCondVar | mozilla::CondVar::Wait(unsigned int)

Categories

(Core :: DOM: Content Processes, defect)

43 Branch
x86_64
Windows
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox43 --- affected
firefox44 --- ?

People

(Reporter: johnp, Unassigned)

References

Details

(Keywords: crash, Whiteboard: KillHard)

Crash Data

Just crashed with this signature (no STR), but looking at the crash stats this started with the September 5th build in which jemalloc4 had been enabled and has je_isqalloc in the stack. atm windows+amd64 only fwiw.

https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=WaitForSingleObjectEx+|+je_isqalloc+|+PR_WaitCondVar+|+mozilla%3A%3ACondVar%3A%3AWait%28unsigned+int%29#tab-reports
This signature is doubly-spurious: the je_isqalloc frame was not really on the stack (it was a bad stack walk), and this was a two-process dump where the server looked at the less-interesting stack.

The "ipc channel error" field may help point this bug in the right direction: it is somewhat of a grab bag but many of them say HangMonitor.
No longer blocks: jemalloc4-by-default
Component: Memory Allocator → DOM: Content Processes
Crash Signature: [@ WaitForSingleObjectEx | je_isqalloc | PR_WaitCondVar | mozilla::CondVar::Wait(unsigned int) ] → [@ WaitForSingleObjectEx | je_isqalloc | PR_WaitCondVar | mozilla::CondVar::Wait(unsigned int) ] [@ WaitForSingleObjectEx | je_isqalloc | PR_WaitCondVar | mozilla::CondVar::Wait ]
Whiteboard: KillHard
Version: Trunk → 43 Branch
There are no crash reports in the last 28 days in the crash signatures provided.
Then let's close this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.