[Webkit-unassigned] [Bug 173789] Add assertions to RefCounted and DeferrableRefCounted to catch thread-safety issues
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Jun 24 03:27:01 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=173789
--- Comment #2 from David Kilzer (:ddkilzer) <ddkilzer at webkit.org> ---
(In reply to Alexey Proskuryakov from comment #1)
> > check for places where RefCountedBase::m_refCount and DeferrableRefCountedBase::m_refCount are being accessed on a
>
> This is legal with locking.
Do you know of any place where we actually lock like this? Seems like locking would be a fairly heavy(?) compared to using atomic operations for m_refCount in ThreadSafeRefCounted.
The other place this is legal is when doing a WTFMove() of an object from one thread to another, such as in a lambda.
I guess if I can't get this to work I should focus on making it easy to build and run tests with ThreadSanitizer instead, which would catch the same issues, but work in the locking case and maybe(?) the WTFMove() case.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170624/b001a34e/attachment-0001.html>
More information about the webkit-unassigned
mailing list