Interpreting ASAN leak detection output

[Scott Kostyshak]

On Tue, Sep 14, 2021 at 11:15:05PM +0200, Jean-Marc Lasgouttes wrote:
> Le 14/09/2021 à 22:22, Scott Kostyshak a écrit :
> > Most of the time I only see the above leak reported. However, I just did something that seemed to trigger a lot more leaks detected. They are all labeled as "indirect leaks" though. Here is the log:
> > 
> >    https://www.dropbox.com/s/d0lxx4jwg0zwuf9/lyx-leaks.txt?dl=0
> 
> I think that there is data (maybe macro table) that we do not bother to
> release on exit. This is not a problem, but we may want to fix it so that
> real leaks are not hidden anymore.

Makes sense.

> I am not sure this is a priority though.

Good point, I think I'll disable the sanitizer for now. It is pretty cool that compiling with the sanitizer doesn't slow LyX down that much (e.g., Valgrind is painful to use). The slowdown is noticeable, but LyX is still useable with it.

Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20210914/f2c4f0c9/attachment.asc>