| Summary: | We should avoid making connections to the GPU Process during garbage collection | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Wenson Hsieh <wenson_hsieh> | ||||
| Component: | Canvas | Assignee: | Wenson Hsieh <wenson_hsieh> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | dino, sabouhallawa, thorton, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Wenson Hsieh
2020-09-29 17:49:39 PDT
Created attachment 410086 [details]
Patch
Comment on attachment 410086 [details]
Patch
memoryCost() and externalMemoryCost() don't do IPC?
also, do we EVER need to make the backing store to answer this question? I'd expect us to know the size up front... I guess it's about IOSurface size rounding or complicated layouts?
Thanks for the review! (In reply to Tim Horton from comment #2) > Comment on attachment 410086 [details] > Patch > > memoryCost() and externalMemoryCost() don't do IPC? Yeah — from what I could gather, memoryCost() and externalMemoryCost() just ask the image buffer backend; however, in the process of creating the backend when using GPUP, we end up also establishing a connection to the GPUP 😬 > > also, do we EVER need to make the backing store to answer this question? I'd > expect us to know the size up front... I guess it's about IOSurface size > rounding or complicated layouts? I think in theory, we shouldn’t; however, the ImageBufferBackend is the thing responsible for keeping track of sizes (and the thing that knows how to estimate memory cost). Committed r267780: <https://trac.webkit.org/changeset/267780> All reviewed patches have been landed. Closing bug and clearing flags on attachment 410086 [details]. |