Created attachment 183515 [details] Examples of file to reproduce leak and leak example Running file conversion using libreoffice or just soffice executable in linux quickly leak a lot of RAM and use all resources of single CPU thread. This leak leaks around ~ 100 MB of RAM per second. CPU usage for single thread is instantly high. File conversion never finishes. PC: Ubuntu 16.04.6 LTS LibreOffice 6.2.8.2 20(Build:2) To reproduce, run cmd (Conversion from DOCX -> DOC): 'libreoffice' '--convert-to' 'doc' '/tmp/d-194ceec5-f443-48d9-9d1d-f825dc87d7f1/result/gened.docx' '--outdir' '/tmp/d-194ceec5-f443-48d9-9d1d-f825dc87d7f1/result' The cause: Seems that when document in word/document.xml contains footnote and text in the same <w:r> tags. To be more specific, this problem only occours when text tag is longer than some limit (see attachments on leak.png and noleak.png) There seems to be no leak when footnotes and text are seperated. Microsoft Word seems to seperate footnotes from text elements. What would be expected: If docx has invalid formatting (if this leak is caused by invalid formatting), then there could be 2 outcomes: 1. Process raises some error and exits 2. Libreoffice tries to fix formatting and then converts file
LO 6.2 is old, please give a try with a recent LO version 7.3.7 or 7.4.2 (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). Also, I think you should upgrade Ubuntu, if you want to stick to LTS, there 22.04.
I have good news, this leak can be 1:1 reproduced in: PC: Ubuntu 22.04.1 LTS LibreOffice 7.4.2.3 40(Build:3) P.S. Sometimes it's not eazy to upgrade to newer versions :)
Thank you for the feedback. On pc Debian x86-64 with master sources updated today, I could reproduce this. Remark: with noleak doc, there's no freeze but the result does'nt correspond to docx. Indeed, the first indice link is just "t" instead of the whole indice text "text text text".
Dear Guntars, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This does not seem to be an issue with current master, not sure when it would have been fixed