Native GpuMemoryBuffer implementation for the phone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Triaged
|
High
|
Unassigned |
Bug Description
We don't have a native GpuMemoryBuffer implementation in Oxide, instead falling back to the software implementation (using shared memory).
chrome://tracing/ shows there's a lot of contention for the GPU thread on the phone, and a not-insignificant cause of this is texture uploads. Having a native GpuMemoryBuffer implementation would significantly improve this.
What we needs is a graphics buffer that we can:
- Rasterize directly to
- Share between processes
- Use as a source for EGLImage
https:/
The attached photo (sorry, no screenshots on Freiza) shows an instance where the GPU thread is blocked for around 10ms just doing texture uploads.
This would also be a significant step towards having a separate GPU process for the browser too.