Intermittent GECKO(5204) | SUMMARY: AddressSanitizer: 454 byte(s) leaked in 2 allocation(s).
Categories
(Core :: General, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox74 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: mccr8)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Filed by: egao [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=284348066&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XR_WWpXHQ-mMaeLkwoXWDg/runs/0/artifacts/public/logs/live_backing.log
suite: mochitest-chrome
chunk: 1
context:
[task 2020-01-10T08:00:29.436Z] 08:00:29 INFO - SimpleTest FINISHED
[task 2020-01-10T08:00:29.988Z] 08:00:29 INFO - GECKO(5204) | 1578643229983 Marionette TRACE Received observer notification xpcom-will-shutdown
[task 2020-01-10T08:00:29.992Z] 08:00:29 INFO - GECKO(5204) | 1578643229984 Marionette INFO Stopped listening on port 2828
[task 2020-01-10T08:00:29.995Z] 08:00:29 INFO - GECKO(5204) | 1578643229984 Marionette DEBUG Marionette stopped listening
[task 2020-01-10T08:00:32.577Z] 08:00:32 INFO - GECKO(5204) | =================================================================
[task 2020-01-10T08:00:32.578Z] 08:00:32 ERROR - GECKO(5204) | ==5204==ERROR: LeakSanitizer: detected memory leaks
[task 2020-01-10T08:00:32.579Z] 08:00:32 INFO - GECKO(5204) | Direct leak of 454 byte(s) in 2 object(s) allocated from:
[task 2020-01-10T08:00:32.580Z] 08:00:32 INFO - GECKO(5204) | #0 0x55cb906ceb9d in malloc /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:145:3
[task 2020-01-10T08:00:32.580Z] 08:00:32 INFO - GECKO(5204) | #1 0x7fd1f128fa7d (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x54a7d)
[task 2020-01-10T08:00:32.580Z] 08:00:32 INFO - GECKO(5204) | -----------------------------------------------------
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | Suppressions used:
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | count bytes template
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | 24 728 nsComponentManagerImpl
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | 4 832 mozJSComponentLoader::LoadModule
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | 633 18083 libfontconfig.so
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | 7 53 libglib-2.0.so
[task 2020-01-10T08:00:32.581Z] 08:00:32 INFO - GECKO(5204) | -----------------------------------------------------
[task 2020-01-10T08:00:32.582Z] 08:00:32 INFO - GECKO(5204) | SUMMARY: AddressSanitizer: 454 byte(s) leaked in 2 allocation(s).
[task 2020-01-10T08:00:32.641Z] 08:00:32 INFO - TEST-INFO | Main app process: exit 0
[task 2020-01-10T08:00:32.641Z] 08:00:32 INFO - TEST-INFO | LeakSanitizer | To show the addresses of leaked objects add report_objects=1 to LSAN_OPTIONS
[task 2020-01-10T08:00:32.642Z] 08:00:32 INFO - TEST-INFO | LeakSanitizer | This can be done in testing/mozbase/mozrunner/mozrunner/utils.py
[task 2020-01-10T08:00:32.642Z] 08:00:32 ERROR - TEST-UNEXPECTED-FAIL | LeakSanitizer | leak at unknown stack
[task 2020-01-10T08:00:32.642Z] 08:00:32 INFO - runtests.py | Application ran for: 0:00:37.221980
[task 2020-01-10T08:00:32.642Z] 08:00:32 INFO - zombiecheck | Reading PID log: /tmp/tmpCD9TJ3pidlog
[task 2020-01-10T08:00:32.643Z] 08:00:32 INFO - ==> process 5204 launched child process 5219
[task 2020-01-10T08:00:32.643Z] 08:00:32 INFO - ==> process 5204 launched child process 5313
[task 2020-01-10T08:00:32.643Z] 08:00:32 INFO - ==> process 5204 launched child process 5320
[task 2020-01-10T08:00:32.644Z] 08:00:32 INFO - ==> process 5204 launched child process 5334
[task 2020-01-10T08:00:32.644Z] 08:00:32 INFO - ==> process 5204 launched child process 5402
[task 2020-01-10T08:00:32.644Z] 08:00:32 INFO - ==> process 5204 launched child process 5409
[task 2020-01-10T08:00:32.645Z] 08:00:32 INFO - ==> process 5204 launched child process 5421
[task 2020-01-10T08:00:32.645Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5313
[task 2020-01-10T08:00:32.645Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5219
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5409
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5320
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5421
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5334
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - zombiecheck | Checking for orphan process with PID: 5402
[task 2020-01-10T08:00:32.646Z] 08:00:32 INFO - Stopping web server
[task 2020-01-10T08:00:32.654Z] 08:00:32 INFO - Stopping web socket server
[task 2020-01-10T08:00:32.674Z] 08:00:32 INFO - Stopping ssltunnel
[task 2020-01-10T08:00:32.695Z] 08:00:32 WARNING - leakcheck | refcount logging is off, so leaks can't be detected!
[task 2020-01-10T08:00:32.695Z] 08:00:32 INFO - runtests.py | Running tests: end.
|
||
Comment 1•5 years ago
|
||
Looks to be a new leak, this specific leaked bytes and allocation combination appears to be unique in this try push:
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&tier=1%2C2%2C3&revision=eb7fca553fdee919f26cb9670b72dea812a89463&searchStr=linux1804%2Casan
:mccr8 - pinging you since you were helpful when I needed help with LeakSanitizer some weeks back.
Between bug 1602689 and this bug, it should address all of the existing leaks for linux1804-64-asan/opt platform variant.
|
Assignee | |
Comment 2•5 years ago
|
||
The stack is pretty useless there. There might be something better we could do, but it looks system library ish enough that I guess I can just whitelist it.
I also noticed that the ASan options don't seem to be set properly. This other leak here has a ton of frames, whereas it is supposed to be limited in order to save memory. That's probably an existing issue. https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=284348081&repo=try&lineNumber=2838
|
|
Assignee | |
Comment 3•5 years ago
|
||
|
|
||
Comment 4•5 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #2)
I also noticed that the ASan options don't seem to be set properly. This other leak here has a ton of frames, whereas it is supposed to be limited in order to save memory. That's probably an existing issue. https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=284348081&repo=try&lineNumber=2838
When you say ASAN options aren't set up properly - it is something to do with the underlying docker image?
|
|
Assignee | |
Comment 5•5 years ago
|
||
(In reply to Edwin Takahashi (:egao, :etakahashi) from comment #4)
When you say ASAN options aren't set up properly - it is something to do with the underlying docker image?
We set malloc_context_size as part of ASAN_OPTIONS in various places:
https://searchfox.org/mozilla-central/search?q=malloc_context_size&path=
That is supposed to limit the stack size you see in these LSan report stacks, but it clearly isn't working here, because there are 60 frames being shown. This probably isn't related to the image upgrade change you are doing, but it is peculiar.
|
|
||
Comment 6•5 years ago
|
||
Interesting - I have other leaks from linux1804 mochitest-devtools-chrome, but that stack seems to be capped at the 32 value I see being set for mochitest/runtests.py:
| Comment hidden (Intermittent Failures Robot) |
|
||
Comment 9•5 years ago
|
||
| bugherder | ||
|
||
Updated•5 years ago
|
Description
•