Move ProxyConfigService construction onto the IO thread.

net/proxy/proxy_config_service.h

Index: net/proxy/proxy_config_service.h
diff --git a/net/proxy/proxy_config_service.h b/net/proxy/proxy_config_service.h
index 5e14995d0933fe615f8d5b1a0eb1dadb877b938e..33d0e148435732df64ba60b6816d1c61fa910e68 100644
--- a/net/proxy/proxy_config_service.h
+++ b/net/proxy/proxy_config_service.h
@@ -61,6 +61,11 @@ class NET_EXPORT ProxyConfigService {
   // X seconds at which point they check for changes. However that has
   // the disadvantage of doing continuous work even during idle periods.
   virtual void OnLazyPoll() {}
+
+  // Called on the main thread to indicate now is the time for shutdown work
+  // that must occur on the main thread.  Its also one of the last safe times
+  // to post shutdown tasks to other browser threads.

[Ryan Sleevi, 2012/10/19 17:56:43]

nit: comment layering violation within net/ "to other browser threads".
BrowserThread is a content/ concept. I'd suggest just saying "threads"

From a high-level perspective though, I'm concerned about introducing the idea
of browser/process shutdown into the net/ layer. It would be much nicer if the
shutdown semantics in net/ just focused on the object lifetimes, rather than the
overall process lifetimes. The fact that there is only one PCS per-process - or
whatever other such - shouldn't alter these semantics.

Most importantly, I think it introduces a real design flaw, in that it forces
every ProxyConfigService to consider living on two threads (the Network thread,
where it's created, and the main thread, where this can be called). I'm really
opposed to this, and tried to work very hard during the Android changes to try
and separate out the objects and give them distinct and clear lifetimes.

+  virtual void StartTearDown() {}
 };
 
 }  // namespace net