On some of my Libreoffice Calc files (in xlsx) format, when I save, it uses up 100% of available memory, causes the HD to read/write continuously and hangs. After some period of time (typicaly 1-5 minutes) it will finish successfully. Only when I close all Libreoffice windows will the memory be released again. Not sure why this is happening (memory leak somewhere?). Interesting the the programs runs just fine and uses less than 1GB of RAM until I tell it to save. The file is large (11.7Mb--there are a couple of scanned files in it, but this happens even without those) with quite a few formulae. I am running Ubuntu 14.04 on a Intel® Core™ i7-3770 CPU @ 3.40GHz × 8 processor with 32 GB of RAM. I have attached one file that typically gives me this problem.
I have tried to attach a file that causes the problem. Not sure if it was sucessfully uploaded. Please let me know if it did not.
Hi Michael, thanks for reporting. There is no attached file, I think there is a limit size to upload. If the problem is visible without the scanned, please create a copy without it and try to attach again.
Created attachment 100424 [details] Sample xlsx format file. This is only 437Kb, still does it and took 15 minutes to save.
(In reply to comment #2) > Hi Michael, thanks for reporting. > > There is no attached file, I think there is a limit size to upload. If the > problem is visible without the scanned, please create a copy without it and > try to attach again. Thanks. I just uploaded a new version that is much smaller. This has been happening for a while now, so I don't think it's specific to the most recent release.
I can reproduce the issue, in: Win7x64 Version: 4.2.3.3 Build ID: 882f8a0a489bc99a9e60c7905a60226254cb6ff0, also with the last versions and master. Maybe it is in relation with a lot of formulas in the last row/column on much of the sheets, deleting those last rows saves is fast. Saving in the native file format (ods), is really fast.
Thanks for catching those formulae in the last rows/columns. Most of the sheets were copied from that 1 template sheet, so most had that. I deleted those rows/columns and it nows saves very quickly. I wish I could use ODS format, but I have to work with Excel users as well. Thanks again. PS I changed this to Resolved/Not a bug. Please change it to the appropriate status if that isn't correct.
Fortunately there is a solution for your issue, but I think there is some kind of bug, why it must take so long with xlsx while saves quickly with ods format?. So let's reopen the bug.
** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Issue persist with: Version: 5.0.3.1 (x64) Build ID: fd8cfc22f7f58033351fcb8a83b92acbadb0749e
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Created attachment 129488 [details] a backtrace I reproduced on both: Version: 5.2.2.2 Build ID: 1:5.2.2-0ubuntu2 CPU Threads: 2; OS Version: Linux 4.9; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group (My debug dev build) Version: 5.4.0.0.alpha0+ Build ID: f35d29c8388744be1f95ec4acfca12eec706911a CPU Threads: 2; OS Version: Linux 4.9; UI Render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group
** 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
Also in 6.1+
still repro in Version: 7.1.0.0.alpha0+ Build ID: 27cf6e73d05ac803d5fc12c53aea20ed53007234 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-07-19_17:34:48 Calc: threaded Julien, can you create your perfgraph for this? Just open file from attach and "Save as" it as XLSX
(In reply to Roman Kuznetsov from comment #15) > ... > Julien, can you create your perfgraph for this? Just open file from attach > and "Save as" it as XLSX perfgraphs are useful only if there's someone to interpret it and to try to fix it. If there's nobody, they just going to rot and become useless because code would have changed a lot.
(In reply to Julien Nabet from comment #16) > (In reply to Roman Kuznetsov from comment #15) > > ... > > Julien, can you create your perfgraph for this? Just open file from attach > > and "Save as" it as XLSX > > perfgraphs are useful only if there's someone to interpret it and to try to > fix it. If there's nobody, they just going to rot and become useless because > code would have changed a lot. But without the perfgraph nobody from devs will not look at it at all =( Of course if you don't have any free time for it then I'm sorry for noise
Created attachment 168408 [details] perf flamegraph Wait and see now... (I think it'd be interesting to create new tags like wantperftrace/haveperftrace)
Created attachment 182504 [details] Flamegraph Here's an update of the Flamegraph on pc Debian x86-64 with master sources updated today + gen rendering.
Taking a look at the Flamegraph, I noticed mxCellTable = new XclExpCellTable( GetRoot() ); (see https://opengrok.libreoffice.org/xref/core/sc/source/filter/excel/excdoc.cxx?r=1d25d32b#564). The ctr of XclExpCellTable does quite a lot of things. First I thought using a mere singleton but since the finalization seems to modify the state of the object, I think we rather need to make copies of the singleton (which corresponds to the original state). Any thoughts here? (BTW, there's the equivalent in ExcTable::FillAsTableBinary).