On Mon, Sep 13, 2021 at 06:36:43PM -0400, Scott Kostyshak wrote: > I was just curious to compile LyX with address sanitizer options > (-fsanitize=address). Now when I exit LyX I get the following: > > ---------------------- > ==352555==ERROR: LeakSanitizer: detected memory leaks > > Direct leak of 256 byte(s) in 1 object(s) allocated from: > #0 0x7efe9a873c47 in __interceptor_malloc > ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145 > #1 0x7efe9375d0c9 (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x220c9) > > Indirect leak of 32 byte(s) in 1 object(s) allocated from: > #0 0x7efe9a873e17 in __interceptor_calloc > ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 > #1 0x7efe9375d93e (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2293e) > > SUMMARY: AddressSanitizer: 288 byte(s) leaked in 2 allocation(s). > ---------------------- > > I don't know how to interpret the output. Does this mean the source of the > leak is in libfontconfig.so? i.e., it's not LyX's fault? > > Scott
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 Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
