Bug 251625
Summary: | [WebGPU] Investigate triple-buffering | ||
---|---|---|---|
Product: | WebKit | Reporter: | Myles C. Maxfield <mmaxfield> |
Component: | WebGPU | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | mwyrzykowski, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Myles C. Maxfield
Does triple buffering buy us anything, or does getCurrentTexture() mean that it isn't actually helpful? If we use triple buffering, how does it integrate with Core Animation's timeline? Should we choose a different renderbuffer selection strategy than a simple round-robin?
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/105235023>
Mike Wyrzykowski
We triple buffer now