Description: Memory usage keeps increasing heavily making changes to a large plain text document (say bold/underline/italic) or removing paragraphs. Release only after 20 seconds or so Steps to Reproduce: 1. Open the attachment 2. Make edits (deleting paragraphs rather effective) and monitor memory usage Actual Results: Steadily increasing memory usage Expected Results: More effective memory management Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha0+ Build ID: d9ad59da50c1172fe98f94370221c9c1b688200a CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-08_23:34:44 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 145509 [details] Example file
@buovjaga Probably another catching issue, with the same root cause as bug 119993 (haven't checked but, looks obvious)
Can you give some more substance to this, was it better before (from my tests does not seem like it), more quantifying statements than "increasing heavily" - say what exactly you do and what the memory is before and after?
Created attachment 145544 [details] Screencast The hold backspace variant seems extremely effective & slow to
(In reply to Telesto from comment #4) > Created attachment 145544 [details] > Screencast > > The hold backspace variant seems extremely effective & slow to The slowness is caused by the single paragraph structure (I reported that some in the past). Fixed be adding some new paragraphs to the document.. but doesn't matter for the memory increase
Created attachment 145568 [details] Example file Better example file (not being one large paragraph)
(In reply to Telesto from comment #6) > Created attachment 145568 [details] > Example file > > Better example file (not being one large paragraph) Used backspace-holding tactic. The memory does not increase in versions prior to 6.2 (or does so very slowly). Bibisected to https://cgit.freedesktop.org/libreoffice/core/commit/?id=aeff83240c88435d11590f5e9c6fe9927a508c6a sw: save more vcl layout calls in SwFntObj But it would seem this is expected as it is about putting layouts to cache?
Miklos advised to close this as dupe of 119992 as he believes limiting the size of the cache will solve both. *** This bug has been marked as a duplicate of bug 119992 ***