Closed
Bug 967933
Opened 10 years ago
Closed 3 years ago
TSan: data race js/src/jsfun.h:433 setUnlazifiedScript (JSFunction::flags_)
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Tracking
()
RESOLVED
FIXED
People
(Reporter: decoder, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tsan])
Attachments
(1 file, 1 obsolete file)
6.04 KB,
text/plain
|
Details |
The attached logfile shows a thread/data race (mozilla-central revision 44ba69cacd7e) detected by TSan (ThreadSanitizer). Typically, races reported by TSan are not false positives, but it is possible that the race is benign. Even in this case though, we should try to come up with a fix unless this would cause inacceptable performance issues. Also note that seemingly benign races can possibly be harmful (also depending on the compiler and the architecture) [1]. If the bug cannot be fixed, then this bug should be used to either make a compile-time annotation for blacklisting or add an entry to the runtime blacklist. [1] http://software.intel.com/en-us/blogs/2013/01/06/benign-data-races-what-could-possibly-go-wrong
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Comment 1•9 years ago
|
||
This race is still around, in a slightly different form. We're racing on JSFunction::flags_ from the bytecode emitter and the jit, which seems a bit sketchy. It's not really obvious to me where the read is coming from, though; the line in the TSan output says MCall::accept, and I don't see how that calls JSFunction::flags(). I'll try and get a better stack.
Attachment #8370446 -
Attachment is obsolete: true
Comment 2•9 years ago
|
||
Reclassifying as a JIT bug, optimistically.
Component: JavaScript Engine → JavaScript Engine: JIT
Summary: TSan: data race js/src/../../js/src/jsfun.h:114 flags → TSan: data race js/src/jsfun.h:433 setUnlazifiedScript (JSFunction::flags_)
Updated•8 years ago
|
Priority: -- → P5
Comment 3•3 years ago
|
||
JSFunction::SetUnlazifiedScript
isn't around anymore, so I'm resolving this bug.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•