diff options
author | alexeypa@chromium.org <alexeypa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 02:38:11 +0000 |
---|---|---|
committer | alexeypa@chromium.org <alexeypa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 02:38:11 +0000 |
commit | 002414c002a132b67937869d52aeb85a0547b639 (patch) | |
tree | 234c353c38668c9ecf598cc5057961704b6f5a9b /tools/valgrind/tsan | |
parent | fbff89f316a9c7f44b0f8e3fd96f37fef1b7c817 (diff) | |
download | chromium_src-002414c002a132b67937869d52aeb85a0547b639.zip chromium_src-002414c002a132b67937869d52aeb85a0547b639.tar.gz chromium_src-002414c002a132b67937869d52aeb85a0547b639.tar.bz2 |
Make sure that the UI window created by base::MessagePumpForUI is destoyed on the same thread (Windows).
Currently the window created base::MessagePumpForUI can be destroyed on a wrong thread. base::MessagePumpForUI is a ref-counted class so it can (and does) outlive the owning base::MessageLoop. As the result DestroyWindow() can be called on a wrong thread. This makes TSAN unhappy and it reports races deep unside user32.dll.
Changes in this CL:
- The message pump is now notified when the owning message loop is being destroyed. The notification is used to free all resources that hve to be released on the base::MessageLoop's thread.
- MessagePumpForUI::ScheduleWork() synchronizes access to the message-only window handle to avoid posting messages to the window during or after its destruction.
BUG=241939
Review URL: https://chromiumcodereview.appspot.com/15709015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207278 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/valgrind/tsan')
-rw-r--r-- | tools/valgrind/tsan/suppressions.txt | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/tools/valgrind/tsan/suppressions.txt b/tools/valgrind/tsan/suppressions.txt index 5d0d847..671e2e8 100644 --- a/tools/valgrind/tsan/suppressions.txt +++ b/tools/valgrind/tsan/suppressions.txt @@ -1126,34 +1126,3 @@ ... fun:media::FFmpegVideoDecoder::Decode } -{ - bug_241939a - ThreadSanitizer:Race - fun:CreateDialogParamW - fun:CharPrevW - fun:SystemParametersInfoW - fun:RegisterClassExW - fun:base::MessagePumpForUI::InitMessageWnd - fun:base::MessagePumpForUI::MessagePumpForUI - fun:base::MessageLoop::MessageLoop - fun:remoting::AutoThread::ThreadMain -} -{ - bug_241939b - ThreadSanitizer:Race - fun:GetWindowLongW - fun:GetWindowLongW - fun:GetWindowLongW - fun:PostMessageW - fun:PostMessageW - fun:SetWindowTextW - fun:KiUserCallbackDispatcher - fun:LoadStringA - fun:LoadStringA - fun:LoadStringA - fun:CreateWindowExW - fun:base::MessagePumpForUI::InitMessageWnd - fun:base::MessagePumpForUI::MessagePumpForUI - fun:base::MessageLoop::MessageLoop - fun:remoting::AutoThread::ThreadMain -} |