diff options
| author | miu <miu@chromium.org> | 2015-03-06 19:14:38 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-03-07 03:15:35 +0000 |
| commit | 365c4b25fb7cfcebf166ca7b24d11561731f5b80 (patch) | |
| tree | 8cf134aaa48c1152eb12bb304c57e2ccd81731c0 /tools | |
| parent | 3849bd2b775e9fa55dc43412b17058ff0c1762f9 (diff) | |
| download | chromium_src-365c4b25fb7cfcebf166ca7b24d11561731f5b80.zip chromium_src-365c4b25fb7cfcebf166ca7b24d11561731f5b80.tar.gz chromium_src-365c4b25fb7cfcebf166ca7b24d11561731f5b80.tar.bz2 | |
Remove software paint FrameSubscriber from tab capture.
All tab capture platforms have supported capture via event-driven
compositor updates for quite a while now. The "notification of backing
store change" code path never triggers, except in certain edge cases
where extra frame captures will be started. The extra frame captures
are bad for the user experience, since the extra frames reduce video
playback smoothness. The extra frame captures were also throwing-off
the "out-of-order frame delivery" logic, causing wanted frames to be
dropped.
BUG=464475
Review URL: https://codereview.chromium.org/989683004
Cr-Commit-Position: refs/heads/master@{#319549}
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions