Fix up ordering in ProfileIOData.
It's important to destroy the ResourceContext before we start destroying the URLRequestContext and the members it owns, because destroying the ResourceContext will cancel the pending URLRequests for that ResourceContext in the ResourceDispatcherHost. Those URLRequests may reference the URLRequestContexts in their destructors, so we need to make sure ResourceContext is destroyed first. While doing this, I did some other cleanup: * discovered that we could eliminate HostContentSettingsMap from ProfileIOData, w00t! * reordered URLRequestContext after the members it points to, so it gets destroyed before they get destroyed * moved the virtuals in ProfileIOData::ResourceContext to be public, since the parent class changed them to be public BUG=90971 TEST=none Review URL: http://codereview.chromium.org/10174008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133793 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment