Closed
Bug 665330
Opened 14 years ago
Closed 10 years ago
Tracemalloc sometimes turns stack exhaustion into "Assertion failure: lock->owner == 0"
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jruderman, Unassigned)
References
Details
Attachments
(1 file)
|
6.19 KB,
text/plain
|
Details |
This happened a few times on test slaves when they hit bug 665209. I don't have a way to reproduce the assertion.
Assertion failure: lock->owner == 0,
at nsprpub/pr/src/threads/combined/prulock.c:212
|
||
Comment 1•10 years ago
|
||
I *think* this would turn a job orange/red if we were still hitting it? Assuming that's true, I'm thinking we should probably just WFM this bug.
Flags: needinfo?(continuation)
|
||
Comment 2•10 years ago
|
||
tracemalloc has been removed
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(continuation)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•