diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-24 00:00:31 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-24 00:00:31 +0000 |
| commit | 9a88c90a08d3b8611d0bd5b46f6299b62a7b5f5d (patch) | |
| tree | 44b4cc62faa701edcff662b676cc081e4e3ea603 /chrome/browser | |
| parent | a1c833f571c913363cc2fbd3400caf3a6f715c14 (diff) | |
| download | chromium_src-9a88c90a08d3b8611d0bd5b46f6299b62a7b5f5d.zip chromium_src-9a88c90a08d3b8611d0bd5b46f6299b62a7b5f5d.tar.gz chromium_src-9a88c90a08d3b8611d0bd5b46f6299b62a7b5f5d.tar.bz2 | |
Check that thread contexts are cleaned up during profiling
There was a Thread Local Store regression, wherein
thread cleanup notifcation was not sent to TLS
users. This CL ensures that when this happens,
that Chrome will crash.
For now, I'm landed with a short-circuit (returns true
all the time) in the test. I'll remove the TODO when
we have XP properly supported.
r=rtenneti
BUG=103209
Review URL: http://codereview.chromium.org/8606001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111451 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser')
| -rw-r--r-- | chrome/browser/browser_process_impl.cc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/chrome/browser/browser_process_impl.cc b/chrome/browser/browser_process_impl.cc index 843cce0..a6e637f 100644 --- a/chrome/browser/browser_process_impl.cc +++ b/chrome/browser/browser_process_impl.cc @@ -285,6 +285,8 @@ BrowserProcessImpl::~BrowserProcessImpl() { // former registers for notifications. tab_closeable_state_watcher_.reset(); + tracked_objects::ThreadData::EnsureCleanupWasCalled(4); + g_browser_process = NULL; } |