VideoFrame::data() and visible_data() should lazy-map the memory |
||||
Issue descriptionCurrently, VideoFrame::WrapExternalStorage() expects both a SharedMemoryHandle and data ptr for creating a VideoFrame. This requires us to map the shmem first to have access to a ptr. This causes an overhead as we are mapping shared memory on time sensitive threads, see GpuVideoEncodeAccelerator::OnEncode() and GpuJpegDecodeAccelerator::OnDecodeOnIOThread(). We should delay this until data ptr are accessed where available.
,
Nov 9 2016
,
Nov 10 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 14 2017
stale bug not being active for > 1 year. |
||||
►
Sign in to add a comment |
||||
Comment 1 by emir...@chromium.org
, Nov 1 2016Status: Started (was: Available)