diff options
| author | davidben@chromium.org <davidben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-19 18:15:38 +0000 |
|---|---|---|
| committer | davidben@chromium.org <davidben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-19 18:15:38 +0000 |
| commit | ef0e26b190c956599a9df6194a992c6e137bf74a (patch) | |
| tree | 6196b86b3b296c404d302087c866745c4d6b45e8 /chrome/browser/policy/cloud/rate_limiter.cc | |
| parent | c19e2ff3cae12fb055ffed194b3a5a9c908cf996 (diff) | |
| download | chromium_src-ef0e26b190c956599a9df6194a992c6e137bf74a.zip chromium_src-ef0e26b190c956599a9df6194a992c6e137bf74a.tar.gz chromium_src-ef0e26b190c956599a9df6194a992c6e137bf74a.tar.bz2 | |
Release prerenders in the PrerenderDispatcher on abandon/cancel.
There's no need to maintain the reference; once abandon or cancel is called,
the LinkLoader (as PrerenderClient) has already been removed from the Prerender
in Blink, so it is no longer consuming didStopPrerender and friends. Rather,
this is causing us to leak cancelled prerenders because the browser process
does not send OnPrerenderStop for canceled prerenders either, leaving nothing
to release PrerenderDispatcher's reference to the Prerender (via WebPrerender).
This introduces the possibility of an OnPrerenderStart from the browser racing
with an (asynchronous) cancel message to the browser, so handle that case.
BUG=290197
Review URL: https://codereview.chromium.org/27195006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229604 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/policy/cloud/rate_limiter.cc')
0 files changed, 0 insertions, 0 deletions