<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Huge ram amount used not freed" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125428#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Huge ram amount used not freed" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125428">bug 125428</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=125428#c24">comment #24</a>) Hi! Although this might need further analysis, I agree that not releasing memory *at all* after an operation (as 7-8 from c#14 might hint) must be treated as a bug. Yet, it needs investigating: is that really not released e.g. on timer? is sorting repeatedly on the same data (e.g. asc->desc->asc->...) produce higher levels after the spike each time? etc. But if it's released subsequently, without unloading documents or exiting program, then IMO it needs much more substantial ground to be called a bug. That would mean proper memory handling, and only if that results in actual problems, the strategy might need to be revised.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>