https://bugs.documentfoundation.org/show_bug.cgi?id=152033

--- Comment #6 from Wolf Icefang <[email protected]> ---
I can back up that I'm having this issue as well, with LibreOffice 7.5.0 and
also 7.4.5, running on my Windows 10 laptop.
Steps to reproduce:
1. Open LibreOffice and put a bunch of text into it, or open a preexisting
file. The file can be less than one page in length, but the bigger the
document, the faster the RAM buildup.
2. Select some text. The more text you select, the more RAM you'll eat up in
step 3.
3. Start scrolling up and down in the document. As you scroll, the RAM usage of
LibreOffice will increase. Deselecting text does not reduce the amount of RAM
used.
4. Eventually, the computer will run out of memory and Windows will start to
kill applications.

Running LibreOffice in safe mode will fix the issue completely, but if I reset
to factory settings and run LibreOffice normally, the issue returns.


Note: In a sufficiently complex document (perhaps related to embedded images,
IDK) LibreOffice will leak memory just from scrolling around, and selecting
text will just make the memory leak happen faster. For example, in a 7 page
document with multiple images, form sections, etc, LibreOffice Writer in Safe
Mode doesn't ever breach 250 MB of RAM usage, but without Safe Mode, scrolling
to the bottom of the document (after selecting all text with Ctrl+A) pushes RAM
usage over 3.1 GB. Scrolling back to the top increases that number to 4.46 GB!

Please bump this bug from "normal" to "major". It causes LibreOffice to crash
and sometimes Windows decides to close other applications as well. I have to
either (a) keep Windows Task Manager on my screen to closely monitor my RAM
usage, or (b) run LibreOffice Writer in Safe Mode for everything.


Version: 7.4.5.1 (x64) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to