Closed
Bug 1253440
Opened 9 years ago
Closed 9 years ago
devtools/client/animationinspector/test TEST-UNEXPECTED-FAIL | LeakSanitizer | leak at Location, mozilla::ipc::MessageChannel::OnMessageReceivedFromLink, OnMessageReceived, mozilla::ipc::ProcessLink::OnMessageReceived
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
FIXED
mozilla48
People
(Reporter: RyanVM, Assigned: nical)
References
(Blocks 2 open bugs)
Details
(Keywords: memory-leak, Whiteboard: btpp-fixlater)
Attachments
(1 file)
2.17 KB,
text/plain
|
Details |
For fun, I decided to run ASAN mochitest-dt on Try with e10s enabled and am seeing this permaleak in the animationinspector tests.
https://treeherder.mozilla.org/logviewer.html#?job_id=17571384&repo=try
14:00:02 INFO - ==2017==ERROR: LeakSanitizer: detected memory leaks
14:00:02 INFO - Direct leak of 160 byte(s) in 10 object(s) allocated from:
14:00:02 INFO - #0 0x475061 in __interceptor_malloc /builds/slave/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:74
14:00:02 INFO - #1 0x48dd0d in moz_xmalloc /builds/slave/try-l64-asan-00000000000000000/build/src/memory/mozalloc/mozalloc.cpp:83
14:00:02 INFO - #2 0x7f6947934ad6 in Location /builds/slave/try-l64-asan-00000000000000000/build/src/obj-firefox/dist/include/mozilla/mozalloc.h:186
14:00:02 INFO - #3 0x7f6947934ad6 in mozilla::ipc::MessageChannel::OnMessageReceivedFromLink(IPC::Message const&) /builds/slave/try-l64-asan-00000000000000000/build/src/ipc/glue/MessageChannel.cpp:765
14:00:02 INFO - #4 0x7f6947947e41 in OnMessageReceived /builds/slave/try-l64-asan-00000000000000000/build/src/ipc/glue/MessageLink.cpp:330
14:00:02 INFO - #5 0x7f6947947e41 in non-virtual thunk to mozilla::ipc::ProcessLink::OnMessageReceived(IPC::Message const&) /builds/slave/try-l64-asan-00000000000000000/build/src/obj-firefox/ipc/glue/Unified_cpp_ipc_glue0.cpp:331
14:00:02 INFO - #6 0x7f69478d78fa in IPC::Channel::ChannelImpl::ProcessIncomingMessages() /builds/slave/try-l64-asan-00000000000000000/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:630
Comment 1•9 years ago
|
||
That stack is not very good. Somebody would probably have to reproduce locally to get better information.
Updated•9 years ago
|
Whiteboard: btpp-fixlater
Comment 3•9 years ago
|
||
The line numbers are basically the same, except it says "operator new" instead of "Location", which makes more sense.
I'm guessing the leaked allocation is the DequeueTask in OnMessageReceivedFromLink:
mWorkerLoop->PostTask(FROM_HERE, new DequeueTask(mDequeueOneTask));
Note that there are a number of other places in the file that do this exact same thing, with the PostTask and a new DequeueTask, and those are apparently not leaking.
Another bit of information that my local run has is that the frame above ProcessIncomingMessages() is IPC::Channel::ChannelImpl::OnFileCanReadWithoutBlocking(int).
Comment 4•9 years ago
|
||
I reproduced this with
./mach mochitest -f mochitest-browser-chrome --e10s devtools/client/animationinspector/test/
Updated•9 years ago
|
Blocks: e10s-tests
Comment 5•9 years ago
|
||
This needs somebody to dig into the IPC code a bit, and I don't have time for that at the moment.
Assignee: continuation → nobody
Reporter | ||
Comment 6•9 years ago
|
||
David, do you have cycles to pick this up?
Flags: needinfo?(dvander)
Reporter | ||
Comment 7•9 years ago
|
||
Maybe jld? This is 100% reproducible on ASAN builds w/ e10s enabled.
Flags: needinfo?(jld)
Comment 8•9 years ago
|
||
I have a build and `./mach mochitest devtools/client/animationinspector` just passed (e10s is the default now). One difference from comment #4 is that the LLVM/Clang build I used is from a newer version than official Firefox ASan builds, but surely that wouldn't affect a memory leak?
I could also try to redo this with (approximately) the same source revision as comment #4 and see if that makes a difference. Thoughts?
Flags: needinfo?(jld)
Comment 9•9 years ago
|
||
(In reply to Jed Davis [:jld] from comment #8)
> I could also try to redo this with (approximately) the same source revision
> as comment #4 and see if that makes a difference.
I tried that. Still can't reproduce the leak.
Reporter | ||
Comment 11•9 years ago
|
||
Fun story, this was actually fixed the other day by bug 1215265.
https://treeherder.mozilla.org/#/jobs?repo=try&fromchange=3968aad4f5d8&tochange=5126d2eeca77&group_state=expanded&filter-searchStr=dt7
Assignee: nobody → nical.bugzilla
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox48:
--- → fixed
Depends on: 1215265
Flags: needinfo?(dvander)
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in
before you can comment on or make changes to this bug.
Description
•