diff options
| author | willchan@chromium.org <willchan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-22 21:24:36 +0000 |
|---|---|---|
| committer | willchan@chromium.org <willchan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-22 21:24:36 +0000 |
| commit | 23056f87ae27274aae0ce642de01c5737b7882f4 (patch) | |
| tree | 09d8c93071a13f11a5f9150e7eacfbb4a883eb20 /chrome_frame/chrome_frame_npapi_entrypoints.cc | |
| parent | 2123cbae0986af60da4159862d7ac10a417de8fd (diff) | |
| download | chromium_src-23056f87ae27274aae0ce642de01c5737b7882f4.zip chromium_src-23056f87ae27274aae0ce642de01c5737b7882f4.tar.gz chromium_src-23056f87ae27274aae0ce642de01c5737b7882f4.tar.bz2 | |
Make sure the service process kills all URLFetcher::Cores on shutdown.
I'm not sure this is strictly necessary, since it may be that due to how the service process uses URLFetcher, that all fetches are already canceled by the time its IO thread shuts down. But this makes absolutely sure this is the case. Good practice in any case.
This also makes it completely safe for us to have URLFetcher::Core stop using the DestructionObserver.
BUG=59630
TEST=existing
Review URL: http://codereview.chromium.org/3969006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63568 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/chrome_frame_npapi_entrypoints.cc')
0 files changed, 0 insertions, 0 deletions