Fix assert that BackgroundDownloader's timer os deleted on wrong thread
The timer and two interface pointers are leaked if a download is
active when the browser is shutting down.
Releasing these resources on the file thread is impractical to do at
this time due to the browser shutdown sequence. The file thread is
terminated before the dtor of this class is called and there is no
obvious way to hook up the shutdown of the browser to terminate a
download in progress and dispose of these resources.
BUG=341083
Review URL: https://codereview.chromium.org/156983005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249662 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/component_updater/component_updater_service.cc b/chrome/browser/component_updater/component_updater_service.cc
index 780354b..2095c05 100644
--- a/chrome/browser/component_updater/component_updater_service.cc
+++ b/chrome/browser/component_updater/component_updater_service.cc
@@ -155,8 +155,8 @@
// the tasks. Also when we do network requests there is only one |url_fetcher_|
// in flight at a time.
// There are no locks in this code, the main structure |work_items_| is mutated
-// only from the UI thread. The unpack and installation is done in the file
-// thread and the network requests are done in the IO thread and in the file
+// only from the UI thread. The unpack and installation is done in a blocking
+// pool thread. The network requests are done in the IO thread or in the file
// thread.
class CrxUpdateService : public ComponentUpdateService {
public:
