Bug 47475

Summary: [OpenVG] VGPath caching
Product: WebKit Reporter: Pierre-Antoine LaFayette <pierre.lafayette>
Component: PlatformAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: jpetsovits, krit, mrobinson
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: All   
Attachments:
Description Flags
Patch ariya.hidayat: review-

Pierre-Antoine LaFayette
Reported 2010-10-10 13:48:46 PDT
Allocation and deallocation of GPU memory for VGPaths is expensive and should be avoided. For primitives whose segment data do not change, we can use vgModifyPathCoords to change the path.
Attachments
Patch (9.01 KB, patch)
2010-10-10 14:32 PDT, Pierre-Antoine LaFayette 		ariya.hidayat: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Pierre-Antoine LaFayette
Comment 1 2010-10-10 14:32:28 PDT
Created attachment 70414 [details] Patch
Dirk Schulze
Comment 2 2010-10-31 13:02:13 PDT
can you wait for bug 48516 please? It's maybe possible to optimize it more after the patch there.
Ariya Hidayat
Comment 3 2010-12-23 11:08:05 PST
Comment on attachment 70414 [details] Patch Bug 48516 has been solved. Pierre, can you update this patch?
Pierre-Antoine LaFayette
Comment 4 2010-12-23 11:17:23 PST
(In reply to comment #3) > (From update of attachment 70414 [details]) > Bug 48516 has been solved. Pierre, can you update this patch? I believe Jakob had said that their latest OpenVG GraphicsContext code uses path caching / transforms when possible. He said they would be upstreaming that new code which would make this patch unnecessary. I had thought they would have updated the OpenVG code by now. They seemed to have abandoned their upstreaming efforts.
Note You need to log in before you can comment on or make changes to this bug.