Closed
Bug 1415093
Opened 8 years ago
Closed 1 year ago
Intermittent Assertion failure: 0 == rv, nsprpub/pr/src/pthreads/ptthread.c:288, PROCESS-CRASH | Main app process exited normally | application crashed [@ mozalloc_abort(char const*)]
Categories
(Core :: General, defect)
Core
General
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: aryx, Unassigned)
References
Details
(Keywords: intermittent-failure)
+++ This bug was initially created as a clone of Bug #1208957 +++
https://treeherder.mozilla.org/logviewer.html#?job_id=142597362&repo=mozilla-inbound
GECKO(2012) | Assertion failure: 0 == rv, at /builds/worker/workspace/build/src/nsprpub/pr/src/pthreads/ptthread.c:870
PROCESS-CRASH | Main app process exited normally | application crashed [@ mozalloc_abort(char const*)]
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 3•8 years ago
|
||
Is it possible that this is the nsHostResolver thread [1]? The stack shows us freeing thread structures after XPCOM shutdown and racing with NSPR shutdown. My understanding is that we should join all threads before XPCOM shutdown to avoid problems like this. See also bug 1208957 (which this is a clone of) where the XPConnect watchdog thread was running into exactly the same problem.
[1] https://searchfox.org/mozilla-central/rev/f0ab0b072ae090f11d6b02b7cf1e0829b4f08882/netwerk/dns/nsHostResolver.cpp#1038
Flags: needinfo?(valentin.gosu)
This is certainly possible.
However, this is a PR_UNJOINABLE_THREAD, so I don't think simply joining the thread would work.
I am currently attempting refactor the DNS code, and am considering using nsIThread instead. But this might take a while.
Flags: needinfo?(valentin.gosu)
Comment 5•8 years ago
|
||
Yeah, in the other bug I had to make the thread a PR_JOINABLE_THREAD.
Given the low failure rate here, I don't think this is a super high priority. I just wanted to make sure you were aware. Is there a bug to follow to track the refactoring work/move to nsIThread?
Depends on: 1426019
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 9•8 years ago
|
||
status-firefox59:
--- → ?
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Severity: normal → S3
Comment 27•1 year ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
| Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•