Open Bug 1159567 Opened 10 years ago Updated 2 years ago

Have a THREAD_POOL_REF_COUNTING THREAD_SAFE_REF_COUNTING macro

Categories

(Core :: Audio/Video: Playback, defect)

defect

Tracking

()

Tracking Status
firefox40 --- affected

People

(Reporter: jya, Unassigned)

Details

Currently we the choice between NS_INLINE_DECL_THREADSAFE_REFCOUNTING and NS_INLINE_DECL_REFCOUNTING NS_INLINE_DECL_THREADSAFE_REFCOUNTING imply that the class is thread safe when it may not be. NS_INLINE_DECL_REFCOUNTING on the other hand while clearly thread safe will assert if the object is deleted on a different thread than it was created on. That makes it unusable in a task queue's thread pool where which thread is actually used to run the task is non predictable. We should have a THREAD_POOL_REF_COUNTING THREAD_SAFE_REF_COUNTING.
Component: Audio/Video → Audio/Video: Playback
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.