Open
Bug 1527453
Opened 6 years ago
Updated 3 years ago
Examine IOInterposer thread safety
Categories
(Core :: Gecko Profiler, enhancement, P2)
Core
Gecko Profiler
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | affected |
People
(Reporter: mozbugz, Unassigned)
References
Details
IOInterposer is probably effectively only used from the main thread (aka MT), but the profiler code currently allows for the possibility of being used off-MT, and with bug 1526357 it is now possible that it could be unregistered before the profiler shuts down (while other IO operations may still happen.)
In particular sMasterList is accessed from most methods without any atomicity nor locking.
So I think we should review the thread safety around IOInterposer, and either add checks to verify that it's always called from one thread, or add proper thread safety.
| Reporter | ||
Comment 1•5 years ago
|
||
Could be useful to profile startup, now that most main-thread IOs have been taken care of.
Priority: P3 → P2
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•