[Webkit-unassigned] [Bug 186269] Make it possible to track unbalanced ref()/deref()

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 4 21:47:34 PDT 2018


--- Comment #3 from Darin Adler <darin at apple.com> ---
I think it might be onerous to have to find somewhere to store a token every time you ref/deref something outside of RefPtr/Ref.

I believe that Xcode (maybe it’s Instruments) has features that do this quite well for retain and release without intrusive changes to the code that calls retain and release. I think we should explore how those work and whether we can hook up ref/deref to that.

But I am certainly not opposed to this on principle. Since we normally use smart pointers and not explicit ref/deref calls. We can just ask people to be even more consistent about always doing that. I would prefer to fix call sites by having them use RefPtr and Ref more rather than by decorating calls to ref and deref with additional macro arguments.

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/20180605/604a26b7/attachment.html>

More information about the webkit-unassigned mailing list