Closed GitMensch closed 2 years ago
Yes, I noticed that sometimes the log was truncated, so I added a “flush” call in my internal repository, but having a better look at the docs, a “shutdown” call is also needed (look here: https://spdlog.docsforge.com/v1.x/0.faq/#memory-leak-detected-when-using-inside-a-shared-library)
fixed (per release notes - shutdown
is now called in the destructor)
Not sure if you've added a close function on unloading the module, if not then there possibly is one. If you do and you think that's done correctly then there's either a possible bug in spdlog (which one of us should forward upstream), which is possibly already solved in the newest version or a "by design decission - the OS cleans that at process exit in any case".
I'd like to know what the issue is, and will use a suppression rule for spdlog in the meantime.
Currently valgrind's memcheck
--leak-check=full --show-leak-kinds=all
says: