[Webkit-unassigned] [Bug 69048] [Chromium] Separate compositor client thread from webkit's main thread

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 11 17:38:16 PDT 2011


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





--- Comment #31 from James Robinson <jamesr at chromium.org>  2011-10-11 17:38:15 PST ---
(From update of attachment 110615)
View in context: https://bugs.webkit.org/attachment.cgi?id=110615&action=review

> Source/WebKit/chromium/src/CCMainThreadImpl.cpp:41
> +bool s_initializedThread = false;
> +WebKit::WebThread* s_clientThread = 0;

it looks like the bool is the same thing as s_clientThread being NULL.

> Source/WebKit/chromium/src/CCMainThreadImpl.cpp:79
> +    else
> +        WTF::callOnMainThread(performTask, task.leakPtr());

why do you need this branch? s_clientThread should always be valid when we get here

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