Crash in mozilla::ipc::MessagePump::Run
Categories
(Core :: IPC, defect)
Tracking
()
Tracking | Status | |
---|---|---|
thunderbird_esr52 | --- | unaffected |
firefox-esr52 | --- | wontfix |
firefox-esr60 | --- | wontfix |
firefox-esr68 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | wontfix |
firefox61 | --- | wontfix |
firefox62 | --- | wontfix |
firefox63 | --- | wontfix |
firefox72 | --- | wontfix |
firefox73 | --- | wontfix |
firefox74 | --- | wontfix |
firefox87 | + | wontfix |
People
(Reporter: skywalker333, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, nightly-community, Whiteboard: qa-not-actionable)
Crash Data
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Reporter | ||
Comment 5•7 years ago
|
||
Reporter | ||
Comment 6•7 years ago
|
||
Reporter | ||
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Comment 9•7 years ago
|
||
Comment 11•6 years ago
|
||
Comment 13•5 years ago
|
||
No longer a top crash but still about 50 crashes a day across channels. I am noticing an increase on the Nightly channel since the beginning of the year.
![]() |
||
Updated•4 years ago
|
![]() |
||
Comment 14•4 years ago
|
||
[Tracking Requested - why for this release]:
Jed: The IPCError variant of the failure is with Nightly 87.0a1 on Windows 10 Developer Preview 10.0.21301 (planned release April or May afaik). Can you investigated and create a new bug if necessary? Nightly's crashes started at the start of February and are continuously increasing.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•2 years ago
|
Comment 15•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criteria:
- Top 5 RDD process crashes on release
- Top 5 socket and utility process crashes on release
- Top 5 desktop browser crashes on Mac on release
For more information, please visit auto_nag documentation.
Comment 16•2 years ago
|
||
Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.
For more information, please visit auto_nag documentation.
Comment 17•2 years ago
|
||
Since the crash volume is low (less than 15 per week), the severity is downgraded to S3
. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment hidden (Intermittent Failures Robot) |
Description
•