Make sure that the UI window created by base::MessagePumpForUI is destoyed on the same thread (Wind…

tools/valgrind/tsan/suppressions.txt

 # There are a few kinds of suppressions in this file.
 # 1. third party stuff we have no control over
 #
 # 2. intentional unit test errors, or stuff that is somehow a false positive
 # in our own code, or stuff that is so trivial it's not worth fixing
 #
 # 3. Suppressions for real chromium bugs that are not yet fixed.
 # These should all be in chromium's bug tracking system (but a few aren't yet).
 # Periodically we should sweep this file and the bug tracker clean by
 # running overnight and removing outdated bugs/suppressions.
@@ skipping 1108 matching lines @@
 }
 {
   bug_239350
   ThreadSanitizer:Race
   fun:av_buffer_unref
   fun:av_frame_unref
   fun:avcodec_decode_video2
   ...
   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
-}