Open
Bug 1505409
Opened 6 years ago
Updated 2 years ago
WorkerPrivate::mParentFrozen accessed from two different threads without synchronization
Categories
(Core :: DOM: Workers, enhancement, P3)
Core
DOM: Workers
Tracking
()
NEW
People
(Reporter: ytausky, Unassigned)
Details
This member is almost always accessed from the WorkerPrivate's parent thread, but when constructing a new WorkerPrivate for a child worker, the parent's mParentFrozen is accessed on the parent's thread [1]. Since no synchronization is used, this is undefined behavior.
(That line seems strange anyway. Maybe it's supposed to be aParent->mFrozen?)
[1] https://searchfox.org/mozilla-central/source/dom/workers/WorkerPrivate.cpp#2676
|
Reporter | |
Updated•6 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•