[Webkit-unassigned] [Bug 66145] [chromium] Assert that main thread and compositor thread are used safely

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 12 11:19:39 PDT 2011


--- Comment #4 from Nat Duca <nduca at chromium.org>  2011-08-12 11:19:39 PST ---
In previous incarnations of this code, I proposed something ~= Chrome's NonThreadSafe<T>. This got shot down... the general idea is that a function should *never* have access to stuff that isn't safe in the first place.

So, my question would be, where in our code do we have a function that can get to pointers at the wrong time?

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list