1028382 - Ignore LSan leaks that involve system libraries

Status: RESOLVED WONTFIX

(Testing :: General, defect)

Description

[Andrew McCreight [:mccr8]]

System libraries don't always free everything they use, so there are a variety of weird little leaks like this:

Direct leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x470ad1 in __interceptor_malloc /builds/slave/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:74
    #1 0x7f82ff1d87ea (/usr/lib/x86_64-linux-gnu/libXrandr.so.2+0x17ea)

...with no more frames shown.  I've added a bunch of these to the suppression list, but it appears the list is not entirely stable.  For instance, libXrandr only showed up for the first time this week.  It would be crummy for somebody to get backed out because of a leak like this.

It should be easy enough to alter the LSan report parser to detect these kinds of leaks and not report an error for them.  Then periodically somebody could go through and add suppressions, to reduce the spamminess of logs.

Comment 1

[Andrew McCreight [:mccr8]]

LSan has been enabled for a little over a month, and new leaks with system libraries hasn't been a problem, so I'm going to WONTFIX this.