[Webkit-unassigned] [Bug 66083] [chromium] Split LayerTextureUpdater into main thread / compositor thread versions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 11 15:30:49 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=66083





--- Comment #8 from Iain Merrick <husky at google.com>  2011-08-11 15:30:50 PST ---
To Enne's earlier reply: yes, the Client pointers are intended to keep things typesafe. But you're right, that leads to some hairy pointer-sharing across threads.

Thinking about it, m_client is only ever used in response to a call from the main thread. So if we're consistent about that, it should be safe. But maybe that isn't any better than just holding the base class pointer elsewhere and casting it.

-- 
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