Created attachment 124820 [details] File with the problem (see description) I just encountered a curious problem : I have an existing file (attached). LO Calc gets stuck (with the CPU getting over the roof to 100% according to a 'top' command in a terminal) if I try to insert a new sheet while I currently am with the existing sheet 'Données horaires traitées' open. But if I attempt to do the same thing with open sheet being 'INSTRUCTIONS', it works fine. I suppose it is connected that there is a lot of rows with calculations in the sheet 'Données horaires traitées' and not in the sheet 'INSTRUCTIONS'.
This file crash LO when loading - Version: 5.2.0.0.alpha0+; win7 I can open file in 5.1.1.3
Just as complement of information, let me add that the version of Linux I use is Linux Mint 17.3 (originally an install of 17.1 but upgraded).
The crash of LO when loading - This seems to have begun at the below commit. Adding Cc: to Tomaž Vajngerl; Could you possibly take a look at this one? Thanks 97d366b4fa31a6aab550dbe001a893c4dd0e5bc3 is the first bad commit commit 97d366b4fa31a6aab550dbe001a893c4dd0e5bc3 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Apr 23 11:43:22 2016 -0700 source 334e2dc9c3da4519e31e0452a40d3a958c401876 source 334e2dc9c3da4519e31e0452a40d3a958c401876 :040000 040000 c13e408787ecb466a4188c9d9542f874625c2882 5a4699218d1c6dc6c60a4b802c613ac207dea93d M instdir author Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> 2016-04-20 13:19:47 (GMT) committer Tomaž Vajngerl <quikee@gmail.com> 2016-04-22 11:27:05 (GMT) commit 334e2dc9c3da4519e31e0452a40d3a958c401876 (patch) tree bfe420e41e0e9c5e7767c4ce657bd5e29192d91f parent cb5438a3d16634eb267584122169758ab2b76930 (diff) opencl: better logging of devices and device selection Original bug no repro in 5.1.1.3, win7 - I can insert new sheet. Mamoth, what's your version of LO?
Hello. I have found another file with which I have the same issue. See new attachment I you position yourself on the sheet 'Évènements' open and ass a new sheet (by clicking the '+' button at the left end of the tabs menu at the bottom of the LO window), it works fine. Now, if you attempt to do the same thing from the sheet 'Agrégats départs triphasés' open, LO gets stuck and killing the process is the only way to recover from this situation. This was tested with LO version 5.1.2.2 under Linux Mint 17.3.
Created attachment 124927 [details] Second file with which the bug occurs
Loads for me - but (very) slowly - takes > 1 minute with a debug-build; I get one progress bar over the top of another one too which is interesting. Takes 5s to switch to the mentioned sheet too =) I guess the weight of this sheet - and re-writing the formualae is the problem; nothing to do with OpenCL. I attach a trace of its behaviour on my Linux machine highlighting the slow pieces. Thanks !
Created attachment 125999 [details] some frames 'finish'ing in gdb don't really finish ...
Inserting a sheet as described takes ~6s on a fairly fast laptop. 70% of the time is spent under EndListening(). Taking. Though the crash during load mentioned above is completely unrelated and should had been a separate bug. Removing regression keyword here.
I'm returning this to the pool. Or actually I think this should be resolved as "works now". I don't see it getting stuck (see last comment). 70% time spent is under EndListening() SfxBroadcaster::Remove() the memmove within std::vector, but there is no real solution to that (tests using a std::list instead made things even slower due to the heap alloc overhead). Unless someone comes up with a beautiful idea how to reorder listeners such that they need to be removed from the end only so there'd be no memmove needed..
** 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
Dear Mamoth, 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
Dear Mamoth, 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
With LO 5.2 I insert in 10 secs, but with 7.2 faster, in 2 sec. Not instant but acceptable. Per comment 9 I close as WFM.