Created attachment 99661 [details] bad allocation when selecting a lot of cells, and deleting them calc crashes (somtetimes) with the text 'Bad Allocation' (see attachement)
When you say "deleting them" do you mean deleting the content or the columns? Also "sometimes" - can you be more specific? Also, what is your operating system and is this a new problem which you don't see in 4.2.4.2 release? marking as NEEDINFO - please give us a bit more detail and then mark the bug as UNCONFIRMED. Thanks!
What i tried to do was: "Find out if a long (in time) operation would influence the Autorecovery" What i did was: 1) I created an calc-sheet (see attachment test4242.ods) 2) I copied cells A3:C3 3) I pasted them to: A4:A1048575 4) Then i pressed Ctrl+Home to get back to the top of my sheet 5) I selected: A4:C1048575, and pressed the 'Delete'-key On 1 of my attempts to do this, i received the 'bad allocation' error. On other attempts, i was not able to save the document after step 5 (Resulting in I/O errors, which i have not copied...) I know that (especially step 3) seems a pretty useless action, But these steps should not be the cause of a problem when working with a calc-sheet. Finally, after Joel's comment, i tested this with 4.2.4.2, and same thing go wrong in this version. (It's not a new bug for 4.3 )
Created attachment 99759 [details] test4242.ods
I was doing this on a Windows7 computer.
updating version to reflect new info - version is oldest version that we can see the bug - we just leave comments to say that it still affects a newer version. Thanks for the info - going to try to reproduce
I got similar results with 4.0.6.2 (Win7 x86) : (In reply to comment #2) > 3) I pasted them to: A4:A1048575 Freeze after that step, about 10 secs > 5) I selected: A4:C1048575, and pressed the 'Delete'-key Freeze then crash Looks those operations consume high resources.
Based on last comment marking as NEW and updating version
** 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.0.5 or 5.1.0) 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: 2016-02-21
First of all, since reporting this bug, some things changed 1) I upgraded Windows 7 to Windows 10 2) I decided to run the 64-bits version of LibreOffice 3) Currently running 5.1.0.3 (x64) The problem still exists (see screenshot) I also changed the number of columns I am copying/pasting to 9, so i change the range in step 3 from A3:C3 to A3:I3 (after putting some values in those columns) and changed the range in step 5 from A4:C1048575 to A4:I1048575 Another thing that might be necessary to get this behavior is changing this: Tools/options/Load/Save/General 'Save Autorecovery every: 1 minutes'
Created attachment 122851 [details] screenshot of error in LO5.1
Two (recent) crashreports: http://crashreport.libreoffice.org/stats/crash_details/ff116ae7-bc3d-452e-9df1-f360c88caa3d http://crashreport.libreoffice.org/stats/crash_details/62ca002c-893f-435e-aac3-ff621798e4fb OS: Windows 10 LibeOffice: 5.2.4.2 (x64)
** 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
Bad allocation repro with libo-master~2018-06-18_00.55.07_LibreOfficeDev_6.2.0.0.alpha0_Win_x86.msi
Dear Luuk, 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
Because i bought meself a new computer since the days i reported this bug, and because this computer is more powerrfull then the previous one, and because this 'bug' is about operations which takes long time (longer than 1 minute, to overlap time set in 'Save autorecovery information every .. minutes') and because this was reported for version 4.0, and currently we have 6.2, I do net see any advantage in trying to reproduce this in version 3.3. Because all of the above, I am suggesting to close this bug (WONTFIX?), which leaves you all to solve bugs which will need more attention, unless 'lots-off-people' are facing issues because of this bug... 😊
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.