Closed
Bug 663301
Opened 13 years ago
Closed 12 years ago
Race condition with setFirstEnter
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: gwagner, Assigned: cdleary)
Details
I just hit the assertion: JS_ASSERT(!firstEnterValid); There is a race condition in the setFirstEnter path because we are not yet in the synchronized mode in js_GC.
Assignee | ||
Comment 1•13 years ago
|
||
(In reply to comment #0) > There is a race condition in the setFirstEnter path because we are not yet > in the synchronized mode in js_GC. Ah, okay, I changed it away from a static local variable, which didn't make any synchronization guarantees, so I assumed that the change would be okay. I'll take assignment to familiarize myself with the threading situation.
Assignee: general → cdleary
Status: NEW → ASSIGNED
Reporter | ||
Comment 2•12 years ago
|
||
This code is gone.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•