Issue 889923 has similar leaks for ECKEncryptedMediaTest in single_process_mash_browser_tests.


And some leaks in mojo code in views_mus_interactive_ui_tests
e.g. ClipboardTest/0.GetSequenceNumber

 =================================================================
 ==28522==ERROR: LeakSanitizer: detected memory leaks
 Indirect leak of 36864 byte(s) in 9 object(s) allocated from:
 #0 0x4e8cb9 in __interceptor_posix_memalign /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/asan_malloc_linux.cc:219:3
 #1 0x2724b3e in base::AlignedAlloc(unsigned long, unsigned long) base/memory/aligned_memory.cc:31:7
 #2 0x24d1a1c in ReadBuffer mojo/core/channel.cc:507:28
 #3 0x24d1a1c in mojo::core::Channel::Channel(mojo::core::Channel::Delegate*) mojo/core/channel.cc:603
 #4 0x2557145 in ChannelPosix mojo/core/channel_posix.cc:104:9
 #5 0x2557145 in mojo::core::Channel::Create(mojo::core::Channel::Delegate*, mojo::core::ConnectionParams, scoped_refptr<base::TaskRunner>) mojo/core/channel_posix.cc:763
 #6 0x256711f in mojo::core::BrokerHost::BrokerHost(int, mojo::core::ConnectionParams, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&) mojo/core/broker_host.cc:38:14
 #7 0x25119f7 in mojo::core::NodeController::SendBrokerClientInvitationOnIOThread(mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&) mojo/core/node_controller.cc:333:11
 #8 0x2529602 in Invoke<void (mojo::core::NodeController::*)(mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, const base::RepeatingCallback<void (const std::__1::basic_string<char> &)> &), mojo::core::NodeController *, mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (const std::__1::basic_string<char> &)> > base/bind_internal.h:516:12
 #9 0x2529602 in MakeItSo<void (mojo::core::NodeController::*)(mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, const base::RepeatingCallback<void (const std::__1::basic_string<char> &)> &), mojo::core::NodeController *, mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (const std::__1::basic_string<char> &)> > base/bind_internal.h:616
 #10 0x2529602 in RunImpl<void (mojo::core::NodeController::*)(mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, const base::RepeatingCallback<void (const std::__1::basic_string<char> &)> &), std::__1::tuple<base::internal::UnretainedWrapper<mojo::core::NodeController>, mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (const std::__1::basic_string<char> &)> >, 0, 1, 2, 3, 4> base/bind_internal.h:689
 #11 0x2529602 in base::internal::Invoker<base::internal::BindState<void (mojo::core::NodeController::*)(mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&), base::internal::UnretainedWrapper<mojo::core::NodeController>, mojo::core::ScopedProcessHandle, mojo::core::ConnectionParams, mojo::core::ports::NodeName, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> >, void ()>::RunOnce(base::internal::BindStateBase*) base/bind_internal.h:658
 #12 0x28b1154 in Run base/callback.h:99:12
 #13 0x28b1154 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) base/debug/task_annotator.cc:101
 #14 0x27317c5 in base::MessageLoop::RunTask(base::PendingTask*) base/message_loop/message_loop.cc:434:46
 #15 0x27324b8 in DeferOrRunPendingTask base/message_loop/message_loop.cc:445:5
 #16 0x27324b8 in base::MessageLoop::DoWork() base/message_loop/message_loop.cc:517
 #17 0x2897df0 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) base/message_loop/message_pump_libevent.cc:210:31
 #18 0x2730624 in base::MessageLoop::Run(bool) base/message_loop/message_loop.cc:386:12
 #19 0x278683d in base::RunLoop::Run() base/run_loop.cc:102:14
 #20 0x27ecd27 in base::Thread::Run(base::RunLoop*) base/threading/thread.cc:262:13
 #21 0x27ed78f in base::Thread::ThreadMain() base/threading/thread.cc:357:3
 #22 0x28908d2 in base::(anonymous namespace)::ThreadFunc(void*) base/threading/platform_thread_posix.cc:80:13
 #23 0x7ff325d1c183 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8183)

The views_mus_interactive_ui_tests should be fixed now. Bug for that was 888533.

this doesn't look related to mash. See issue 793426. xhwang@ can you confirm?

I see that the tests were disabled due to flake for desktop linux but not chrome os. However I see plenty of flake on chrome os asan/lsan (non mash). For example, browser_tests in https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/29898

have some failures (although they're green overall because of passing re-runs)

Here is the first part of the failing output (complete output is really long): https://paste.googleplex.com/6534975289556992

I believe this is a dup of 889923. I'm closing as such.