ColinLeeo commented on issue #211: URL: https://github.com/apache/tsfile/issues/211#issuecomment-2295171322
From the screenshot above. 1. Due to the encapsulation of memory usage in the program, valgrind can only collect our underlying memory allocations and cannot determine where the memory is going. 2. The memory usage of the method that alternates between writing and flushing should be smaller, but there may be a situation where memory has not been released. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
