Closed Bug 1156112 Opened 10 years ago Closed 9 years ago

Linux64 asan bc1 is leaking and still green

Categories

(Testing :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(firefox40 affected)

RESOLVED DUPLICATE of bug 1074317
Tracking Status
firefox40 --- affected

People

(Reporter: Gijs, Unassigned)

Details

I haven't investigated this further and/or how long this is the case, but it seems wrong... e.g. https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=a32e3b93c8d8 https://treeherder.mozilla.org/logviewer.html#?job_id=1355929&repo=mozilla-central SUMMARY: AddressSanitizer: 144 byte(s) leaked in 2 allocation(s). SUMMARY: AddressSanitizer: 576 byte(s) leaked in 8 allocation(s). and https://treeherder.mozilla.org/logviewer.html#?job_id=1357184&repo=mozilla-central SUMMARY: AddressSanitizer: 288 byte(s) leaked in 4 allocation(s). SUMMARY: AddressSanitizer: 432 byte(s) leaked in 6 allocation(s). SUMMARY: AddressSanitizer: 720 byte(s) leaked in 10 allocation(s). Can we either ensure this doesn't show up in logs if it's not harmful, or ensure it turns the machine orange or whatever so it gets investigated and fixed etc. ? :-) I'm not really sure where this goes, so please move as appropriate...
These are whitelisted leaks. AFAIK, there's no way to suppress them.
Can you help with this one, please?
Component: Untriaged → General
Flags: needinfo?(choller)
Product: Core → Testing
I don't know anything about leaks and ASan. :mccr8 is probably a better person to ask, forwarding.
Flags: needinfo?(choller) → needinfo?(continuation)
We used to ignore indirect leaks. That's probably what this was. I don't see any in a current bc1 ASan log.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(continuation)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.