Closed
Bug 1347056
Opened 8 years ago
Closed 2 years ago
Crash in mozilla::TaskQueue::Dispatch
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: ting, Unassigned)
References
Details
(Keywords: crash, stale-bug)
Crash Data
This bug was filed from the Socorro interface and is
report bp-0a8503fd-cad8-429e-b635-538e62170313.
=============================================================
Top #13 of Nightly 20170312030213 on Windows, 7 crashes from 2 installations. There're 24 reports on 55 in the past week.
Comment 2•8 years ago
|
||
MOZ_RELEASE_ASSERT(aFailureHandling == DontAssertDispatchSuccess || ((bool)(!!(!NS_FAILED_impl(rv)))))
It means someone tried to dispatch tasks to a task queue that had been shut down.
mozilla::detail::RunnableMethodImpl<mozilla::net::CacheFileIOManager* const, nsresult ( mozilla::net::CacheFileIOManager::*)(void), 1, 0>::Run()
I think that "someone" is CacheFileIOManager.
Flags: needinfo?(jwwang)
Updated•8 years ago
|
Component: XPCOM → Networking: Cache
Updated•8 years ago
|
Assignee: nobody → michal.novotny
Whiteboard: [necko-active]
Comment 3•8 years ago
|
||
I don't think it is CacheFileIOManager. We don't use task queues at all in netwerk code. Looks like a wrong stack.
Assignee: michal.novotny → nobody
Component: Networking: Cache → Untriaged
Whiteboard: [necko-active]
Comment 4•8 years ago
|
||
It seems Audio/Video: Playback related.
Component: Untriaged → Audio/Video: Playback
Updated•7 years ago
|
Priority: -- → P1
Comment 5•7 years ago
|
||
JW, how can you check with the windows stack trace the name of the taskqueue ? (ref bug 1359309)
Flags: needinfo?(jwwang)
Comment 6•7 years ago
|
||
No. I expect it to show up in the "MOZ_CRASH Reason" field.
Flags: needinfo?(jwwang)
This is a P1 bug without an assignee.
P1 are bugs which are being worked on for the current release cycle/iteration/sprint.
If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Comment 8•7 years ago
|
||
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Comment 9•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 10•2 years ago
|
||
Since the crash volume is low (less than 5 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.
Severity: critical → S3
Comment 11•2 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•