[Webkit-unassigned] [Bug 54330] New: [chromium] Cannot use multiple accelerated 2D canvas' in the same render process

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 11 18:08:50 PST 2011


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

           Summary: [chromium] Cannot use multiple accelerated 2D canvas'
                    in the same render process
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: vangelis at chromium.org
                CC: reed at google.com, senorblanco at chromium.org,
                    jamesr at chromium.org


This is an issue with the accelerated Skia path (ENABLE(SKIA_GPU)) only.

Canvas elements residing in different pages handled by the same Render process all share one GrContext (globally allocated per process) but use different GL contexts (one SharedGraphicsContext3D per page) to draw. This appears to be breaking an assumption in the code that all canvas' using the same GrContext must draw via the same GL context too (which allows for proper state tracking).

An easy way to reproduce a failure is to run chrome in --single-process mode and in two different tabs open pages that contain a canvas element.  The first tab will work fine but the second one won't.

We should either create a new GrContext per SharedGraphicsContext3D or use a single SharedGraphicsContext3D per process.

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