diff options
| author | mad@chromium.org <mad@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-19 14:37:06 +0000 |
|---|---|---|
| committer | mad@chromium.org <mad@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-19 14:37:06 +0000 |
| commit | 4dffabe508e0eb554b87d1943373cadb7ca441ed (patch) | |
| tree | faba6dfad08f3dca26f84d7c3cf2645005763421 /chrome/browser/profiles/profile_manager.h | |
| parent | 88d48e6c8ae16dd8543e3c1e3d8ec1e5e082b56c (diff) | |
| download | chromium_src-4dffabe508e0eb554b87d1943373cadb7ca441ed.zip chromium_src-4dffabe508e0eb554b87d1943373cadb7ca441ed.tar.gz chromium_src-4dffabe508e0eb554b87d1943373cadb7ca441ed.tar.bz2 | |
Also delay regular profile destruction...
A previous CL delayed the destruction of Off The Record profiles, but there are cases where they are delayed post destruction of their original profile... no good...
So we now delay the destruction of both the off the record profile and it's original profile when either of them is still referenced by a render process host.
BUG=114245
TEST=unittest --gtest_filter=ProfileDestroyerTest.*
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=123082
Got reverted because of failures in extension api tests, so trying again with fix in extension tests to avoid an infobar leak, which was keeping a render process host alive for too long and causing an assert that not all profiles were destroyed...
Review URL: https://chromiumcodereview.appspot.com/9420036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138038 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/profiles/profile_manager.h')
| -rw-r--r-- | chrome/browser/profiles/profile_manager.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chrome/browser/profiles/profile_manager.h b/chrome/browser/profiles/profile_manager.h index 22219e9..40e0bca 100644 --- a/chrome/browser/profiles/profile_manager.h +++ b/chrome/browser/profiles/profile_manager.h @@ -224,7 +224,7 @@ class ProfileManager : public base::NonThreadSafe, : profile(profile), created(created) { } - ~ProfileInfo() {} + ~ProfileInfo(); scoped_ptr<Profile> profile; // Whether profile has been fully loaded (created and initialized). |