diff options
| author | timurrrr@chromium.org <timurrrr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-31 08:46:44 +0000 |
|---|---|---|
| committer | timurrrr@chromium.org <timurrrr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-31 08:46:44 +0000 |
| commit | df0a0bfe0ea219ede803adfd600d95584d6e8c0d (patch) | |
| tree | dddb7fda49aeefabd463ff48cc87dd6df18e892a /chrome/browser/crash_recovery_browsertest.cc | |
| parent | 0a1a4543882c0cf8b73a44d4d79f36c4e6d77fe9 (diff) | |
| download | chromium_src-df0a0bfe0ea219ede803adfd600d95584d6e8c0d.zip chromium_src-df0a0bfe0ea219ede803adfd600d95584d6e8c0d.tar.gz chromium_src-df0a0bfe0ea219ede803adfd600d95584d6e8c0d.tar.bz2 | |
Suppress reports on benign race on vfptr in ChromeThread.
This has started showing up on TSan/Linux/unit like this:
WARNING: Possible data race during write of size 4 at 0xAEF33E0: {{{
T0 (locks held: {}):
#0 ChromeThread::~ChromeThread() chrome/browser/chrome_thread.cc:44
#1 ImageLoadingTrackerTest::~ImageLoadingTrackerTest() chrome/browser/extensions/image_loading_tracker_unittest.cc:17
#2 ImageLoadingTrackerTest_Cache_Test::~ImageLoadingTrackerTest_Cache_Test() chrome/browser/extensions/image_loading_tracker_unittest.cc:95
#3 testing::internal::TestInfoImpl::Run() testing/gtest/src/gtest.cc:2319
Concurrent read(s) happened at (OR AFTER) these points:
T462 (Chrome_IOThread) (locks held: {}):
#0 base::Thread::ThreadMain() base/thread.cc:156
#1 ThreadFunc(void*) base/platform_thread_posix.cc:26
#2 ThreadSanitizerStartThread ts_valgrind_intercepts.c:571
}}}
http://build.chromium.org/buildbot/memory/builders/Linux%20Tests%20(tsan)/builds/3340
TBR=glider
BUG=25385
Review URL: http://codereview.chromium.org/1572008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@43189 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/crash_recovery_browsertest.cc')
0 files changed, 0 insertions, 0 deletions