Created attachment 116861 [details] Screen shot of frozen LO Writer with RAM monitor rocketing In the attached document, when the frame (containing text starting with "cartoonesque...") is moved with the mouse across the page boundary to bottom of previous page, then the action is undone with CTRL-Z, then the RAM usage of LO goes through the roof (see attached screeenshots) and if user is not quick enough the PC can become unusable. Note that the frame is linked to two other frames (previous and next) for text flow between the three. This bug (and others) happened so regularly while working on this document, that in desperation I resorted to creating a macro to do incremental automatic saves of the document to avoid loosing too much work... OS: Ubuntu 14.10 RAM: 8GB CPU: 64bit Intel® Core™ i7-2720QM CPU @ 2.20GHz × 8 LO: Version: 4.3.7.2 Build ID: 430m0(Build:2) This bug was also experienced with other older versions of LO (I don't have access right now to the other PCs to provide the other version IDs)
Created attachment 116862 [details] Screenshot with TOP showing RAM leaking LO process
Sorry, turns out I can't submit the Writer document (10.8MB). I can send it if requested.
Could you try a more recent LO version (last one is 4.4.3) by using LO ppa? (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa) Indeed 4.3 branch is EOL, see https://wiki.documentfoundation.org/ReleasePlan
(In reply to Julien Nabet from comment #3) > Could you try a more recent LO version (last one is 4.4.3) by using LO ppa? > (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa) > Indeed 4.3 branch is EOL, see https://wiki.documentfoundation.org/ReleasePlan I have added the ppa, updated LO to Version: 4.4.3.2 Build ID: 40m0(Build:2), rebooted the PC, and opened the .odt file again: the bug is exactly the same (very fast RAM leakage leaving very little time to react and close the "not responding application"). If you wish to try by yourself, I have uploaded the file here: http://biologie.univ-mrs.fr/upload/p1/tpe_20150214_ex2.odt Not only that, but now my document has also become unreadable in version 4.4.3.2 because of some unexplainable change in the background color of the frames... Separate bug report on the way. I've spent all my Saturday afternoon (Asia here) filing three LO bug reports. I'm really sorry, I'm very aware how much effort is going into this huge project, but I can't continue filing bug reports, I need to produce documents, this is a very sad day for me but after 15 years of using 100% open source (I switched to OO in 2000!) I'm having to switch to other solution - breaks my heart believe me as I'm such a strong advocate of OS :(
I uploaded your file and tested with LO Debian package 4.4.4 RC2. I found "cartoonesque" in "L'avis de l'expert", page 24. I moved the frame on previous page then did an undo with Ctrl-Z, nothing special about memory. Perhaps I missed something. For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)? Indeed, there could be buggy remnants from previous LO version or from buggy extensions. Normally I would have proposed prerelease version - eg: https://fr.libreoffice.org/download/pre-releases/ - but since it's not for personal use and you lack time, I can easily understand you wouldn't want to try)
(In reply to Julien Nabet from comment #5) > I uploaded your file and tested with LO Debian package 4.4.4 RC2. > I found "cartoonesque" in "L'avis de l'expert", page 24. > I moved the frame on previous page then did an undo with Ctrl-Z, nothing > special about memory. Perhaps I missed something. > > For the test, could you rename your LO directory profile (see > https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)? > Indeed, there could be buggy remnants from previous LO version or from buggy > extensions. > > Normally I would have proposed prerelease version - eg: > https://fr.libreoffice.org/download/pre-releases/ - but since it's not for > personal use and you lack time, I can easily understand you wouldn't want to > try) I have moved my profile: mv .config/libreoffice/ .config/libreoffice_bak The crash happens in exactly the same predictable way. I'm attaching a screenshot of the two very simple actions required to reproduce the crash. It works 100% of the time. Notice the RAM graph in green in the unity monitor.
Created attachment 116875 [details] Screen cast of the two action needed to reproduce the crash. The CTRL-Z key is pressed after the frame is moved.
Thank you for the screencast, I could reproduce this with LO Debian package thanks to it. I'm building right now master sources (future 5.1.0) and it'll take some time (more precisely, some hours) to finish. I'll give a try with it, certainly I may have more info for devs (backtrace, warning logs, etc) since I build with --enable-dbgutil flag. Just for curiosity, what are the other bugtrackers you filled? I could take a look at them.
(In reply to Julien Nabet from comment #8) > Thank you for the screencast, I could reproduce this with LO Debian package > thanks to it. > > I'm building right now master sources (future 5.1.0) and it'll take some > time (more precisely, some hours) to finish. > I'll give a try with it, certainly I may have more info for devs (backtrace, > warning logs, etc) since I build with --enable-dbgutil flag. > Just for curiosity, what are the other bugtrackers you filled? I could take > a look at them. Thanks for the lightening fast pick up of the issue! The other two bugs filed are: -Issue with background formatting of frames in Writer, discovered when I updated to 4.4.3.2 as suggested here for the RAM leakage bug: https://bugs.documentfoundation.org/show_bug.cgi?id=92379 -Issue with cropped images loosing their size ratio in Impress: https://bugs.documentfoundation.org/show_bug.cgi?id=92375
Just for the record, here are some console logs with master sources updated today: warn:legacy.tools:15185:1:xmloff/source/draw/shapeimport.cxx:811: Shape sorting failed warn:legacy.osl:15185:1:sw/source/core/text/porlin.cxx:221: SwLinePortion::FindPrevPortion: blowing in the wind warn:xmloff.core:15185:1:xmloff/source/core/xmlimp.cxx:1438: duplicate style name of family 300: "Sans_20_nom1" warn:legacy.osl:15185:1:xmloff/source/core/xmlerror.cxx:181: An error or a warning has occurred during XML import/export! Error-Id: 0x10040001 Flags: 1 WARNING Class: 4 API Number: 1 Parameters: 0: Exception-Message: empty style name reference Position: Public Identifier: System Identifier: Row, Column: 2,206960 warn:legacy.osl:15185:1:xmloff/source/core/xmlerror.cxx:181: An error or a warning has occurred during XML import/export! Error-Id: 0x10040001 Flags: 1 WARNING Class: 4 API Number: 1 Parameters: 0: Exception-Message: empty style name reference Position: Public Identifier: System Identifier: Row, Column: 2,206960
Some testing show CPU at 100% when undoing and RAM is ok. I retrieved a bt: #0 0x00002aaac9a96970 in SwCacheObj::GetPrev() (this=0x7354a90) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/inc/swcache.hxx:149 #1 0x00002aaac9a948a9 in SwCache::Check() (this=0x2c01720) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/bastyp/swcache.cxx:45 #2 0x00002aaac9a96589 in SwCache::SetLRUOfst(unsigned short) (this=0x2c01720, nOfst=300) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/bastyp/swcache.cxx:412 #3 0x00002aaaca465f10 in SwSaveSetLRUOfst::SwSaveSetLRUOfst(SwCache&, unsigned short) (this=0x7fffffff45f0, rC=..., nOfst=300) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/inc/swcache.hxx:127 #4 0x00002aaaca45d828 in SwViewShell::LayoutIdle() (this=0x2d1dca0) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/view/viewsh.cxx:699 #5 0x00002aaac9c7db4c in sw::DocumentTimerManager::DoIdleJobs(Idle*) (this=0x2c53da0, pIdle=0x2c53db8) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/doc/DocumentTimerManager.cxx:119 #6 0x00002aaac9c7d863 in sw::DocumentTimerManager::LinkStubDoIdleJobs(void*, Idle*) (instance=0x2c53da0, data=0x2c53db8) at /home/julien/compile-libreoffice/libreoffice/sw/source/core/doc/DocumentTimerManager.cxx:81 #7 0x00002aaab1997e55 in Link<Idle*, void>::Call(Idle*) const (this=0x2c53dd8, data=0x2c53db8) at /home/julien/compile-libreoffice/libreoffice/include/tools/link.hxx:127 #8 0x00002aaab1f94975 in Idle::Invoke() (this=0x2c53db8) at /home/julien/compile-libreoffice/libreoffice/vcl/source/app/idle.cxx:26 #9 0x00002aaab1f9bd68 in ImplSchedulerData::Invoke() (this=0x2e746b0) at /home/julien/compile-libreoffice/libreoffice/vcl/source/app/scheduler.cxx:38 #10 0x00002aaab1f9c02d in Scheduler::ProcessTaskScheduling(bool) (bTimer=false) at /home/julien/compile-libreoffice/libreoffice/vcl/source/app/scheduler.cxx:127 #11 0x00002aaab1fc0b0c in ImplYield(bool, bool, unsigned long) (i_bWait=true, i_bAllEvents=false, nReleased=0) at /home/julien/compile-libreoffice/libreoffice/vcl/source/app/svapp.cxx:347 Michael: any thought? Could it be due to timer rework? Layout or cache pb?
Can already be reproduced in OOo 3.3. The mem leak might not hit with the first try, but a second one did it. I also tested with 3.5.0 and 4.0.6. Ubuntu 15.04 64-bit OpenOffice.org 3.3.0 OOO330m20 (Build:9567)
The testing file (comment 4) isn't available anymore
Pascal: can you attach the file? Our upload limit is now 30 megabytes.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to Buovjaga from comment #14) > Pascal: can you attach the file? Our upload limit is now 30 megabytes. Hi, Sorry I must have missed this request for the testing file. I'm attaching it now that the size limit has been increased.
Created attachment 147292 [details] LO Writer file to reproduce the bug
(In reply to Pascal Hingamp from comment #16) > (In reply to Buovjaga from comment #14) > > Pascal: can you attach the file? Our upload limit is now 30 megabytes. > > Hi, > Sorry I must have missed this request for the testing file. I'm attaching it > now that the size limit has been increased. Please note that the testing file is impossible to open in my current LO Writer (Writer hangs after usual "macro warning" - I have to kill LO): Version: 6.0.6.2 Build ID: 1:6.0.6-0ubuntu0.18.04.1 CPU threads: 32; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group
(In reply to Pascal Hingamp from comment #18) > Please note that the testing file is impossible to open in my current LO > Writer (Writer hangs after usual "macro warning" - I have to kill LO): I opened bug 122272 for it. Let's hope for a swift resolution so we can get back to testing the original issue.
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/e7fb44b8c86b4dce1d4c6f15752cc3bf62b14888%5E%21 crashtesting: failure on layout of tdf92372-4.odt It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
After the recent commit, the file no longer hangs in any way. Pascal is invited to test with a fresh build: https://dev-builds.libreoffice.org/daily/master/ I think the newest Linux build might not be new enough. https://wiki.documentfoundation.org/Installing_in_parallel/Linux Arch Linux 64-bit Version: 6.3.0.0.alpha1+ Build ID: b004b7f3c1a28ebab1823bdbe38660b6c44483b1 CPU threads: 8; OS: Linux 5.1; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 22 May 2019
Still hangs if I replicate the screencast Version: 6.3.0.0.alpha1+ Build ID: e7fb44b8c86b4dce1d4c6f15752cc3bf62b14888 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/07642832e3d9c3d1648324ef40bff09bfde1f6e5%5E%21 crashtesting: failure on layout of tdf92372-4.odt It will be available in 6.2.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Dear Pascal Hingamp, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug