Once we move local surface id allocation into the renderer process,
DelegatedFrameHost can no longer create a new local surface id on frame
eviction. This would normally break a few things but after
https://codereview.chromium.org/2736053004/ we should be good.
I tried testing this CL by setting the maximum number of saved
frames to 1 so that each new tab causes the eviction of the previous tab
and compared the current behaviour vs behaviour after this CL and did
not notice any difference. Without https://codereview.chromium.org/2736053004/
if you switch tabs fast enough DCHECKs will fail in SurfaceManager for allocating
a surface using a surface id that is already in use, but that CL fixes
this issue.
TBR=jam@chromium.org
BUG=697864
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
Review-Url: https://codereview.chromium.org/2731793002
Cr-Commit-Position: refs/heads/master@{#456180}
3 files changed
