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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 12 10:20:39 PDT 2011


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

           Summary: [chromium] Assert that main thread and compositor
                    thread are used safely
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: husky at google.com


Our threaded compositor has three modes of operation.

Paint: rendering content using standard WebKit calls. This happens on the main thread.
Commit: pushing data over to the compositor tree. The two threads are synchronized.
Update: presenting content on the screen using GL calls. This happens on the compositor thread.

Each mode involves a fairly complex traversal of the layer tree and/or compositor tree. There may be hidden bugs because we don't actually have a compositor thread yet. We should add asserts to check that methods are called in the appropriate mode(s).

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