Description: Loaded the attached ZIPped RTF (filesizes l.zip: 746kb, l.rtf: 6,729kb) and then looked at the RAM used using MS Process Explorer, for both Writer (Version: 7.3.1.3 (x64) / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: CL) as well as Word (Word 2002) Look at the screen print, and cry. It's just utterly inexcusable that editing a 6Mb file required more than 800Mb. It's actually even worse if the RTF file is first saved (just as RTF) without making any changes to it. In that case amount of RAM required balloons up to MORE THAN ONE GIGABYTE! Steps to Reproduce: 1. Unzip l.zip 2. Open it in Writer and Word 3. Notice the differences in RAM used Actual Results: Utterly ridiculous amounts of RAM used, more than 100 times the size of the input file! Expected Results: Way less Reproducible: Always User Profile Reset: No Additional Info: When are the LO developers finally going to do so about issues like this? If you want people with less capable hardware to use the product, this is not the way to go!
Created attachment 179139 [details] ZIP'ed RTF file that fills the available RAM Just a simple RTF file of about 1500 pages, with just some text bolded, nothing more, nothing less!
Created attachment 179140 [details] Screenprint od RAM used by Word 2002 and Writer Screen-print png from MS Process Explorer showing the vast difference in RAM used between Word and Writer
On pc Debian x86-64 with master sources updated today, I waited some seconds to just open it and saw this log repeating: warn:legacy.osl:17580:17580:writerfilter/source/dmapper/DomainMapper_Impl.cxx:1704: no style sheet found Miklos: thought you might be interested in this one since it concerns rtf.
Created attachment 179150 [details] Flamegraph Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today + gen rendering. (without enable-dbgutil) Flamegraph is rather for perf pb not for RAM use but since it took some time when opening it with my other local build (with enable-dbgutil).