Hi Ilya, On Fri, May 03, 2019 at 06:58:19PM +0500, ???? ??????? wrote: > *** h1 0.1 debug| #0 0x6db986 in update_log_hdr src/log.c:1399 (...) > *** h1 0.1 debug|previously allocated by thread T0 here: > *** h1 0.1 debug| #0 0x7f8ebd15c5de in realloc > (/lib64/libasan.so.5+0x10e5de) > *** h1 0.1 debug| #1 0x6dbd31 in my_realloc2 > include/common/standard.h:1432 > *** h1 0.1 debug| #2 0x6dbd31 in init_log_buffers src/log.c:1880 > *** h1 0.1 debug| > *** h1 0.1 debug|SUMMARY: AddressSanitizer: heap-use-after-free > src/log.c:1399 in update_log_hdr
Nice catch, even affects 1.8. Now fixed. > *** h1 0.1 debug|==23684==ERROR: LeakSanitizer: detected memory leaks > *** h1 0.1 debug| > *** h1 0.1 debug|Direct leak of 24 byte(s) in 1 object(s) allocated > from: > *** h1 0.1 debug| #0 0x7f9ac626f1a8 in __interceptor_malloc > (/lib64/libasan.so.5+0x10e1a8) > *** h1 0.1 debug| #1 0x7f9ac6076b1b (/lib64/libssl.so.1.1+0x33b1b) > *** h1 0.1 debug| > *** h1 0.1 debug|SUMMARY: AddressSanitizer: 24 byte(s) leaked in 1 > allocation(s). For this one I suspect that one object allocated by openssl was expected to be freed by us. I have no idea what this is though. Thanks! Willy
