Closed Bug 1260891 Opened 5 years ago Closed 5 years ago
Acquire and release the lock when destorying an `Exclusive
Data<T>`'s protected value
Even if there is not a traditional race between uses of the protected data and the `ExclusiveData<T>`'s destruction, the thread running the destructor has no guarantee that its cache is up to date with changes already made by other threads. The new acquire and release surrounding the destructor ensures that the destructor doesn't run on stale cache lines.
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
Attachment #8736482 - Flags: review?(terrence) → review+
You need to log in before you can comment on or make changes to this bug.