https://bugs.documentfoundation.org/show_bug.cgi?id=125428
--- Comment #25 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to Telesto from comment #24)
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.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
