When you have a large spreadsheet with, say, 100K rows of a dozen columns or so, and have done Control-A Control-C (which also take a long time), when exiting LibreOffice it takes a very long time (like several minutes) for the soffice.bin process to actually finish, even if the LibreOffice GUI has already gone away. During that time you can't start a new LibreOffice instance either.
A bit over 100k rows, 14 columns. GUI disappeared, but soffice.bin stayed in the process view. After a couple of minutes, there was a message that LibO had crashed. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 902255645328efde34ddf62227c8278e8dd61ff0 TinderBox: Win-x86@39, Branch:master, Time: 2015-07-30_03:52:07 Locale: en-US (fi_FI)
Migrating Whiteboard tags to Keywords: (perf)
Hmm, I can't really reproduce this with callgrind. What I see is that after CTRL+C the overlay code is running amok in calc. But that does not really explain what you see in the shutdown case. Can someone give me a step by step instruction set with a document that works in master?
Ok, after fixing the overlay issue I can reproduce it. It is a gtk issue with the clipboard handling. The termination listener tells gtk to flush the clipboard which somehow tries to store the clipboard content. I'm not sure who is at fault here. I suppose the idea here is that you can still paste after the application has been closed but of course that is going to be an issue when a whole sheet has been selected.
** 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.2.7 or 5.3.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-20170522
My take here is WF/NOB following comment 4.
(In reply to Heiko Tietze from comment #6) > My take here is WF/NOB following comment 4. Or a solution as requested here: bug 112537