Description: It closes when you delete columns from a file with 28101 lines. Actual Results: Any Expected Results: Open Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: tr Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes Builds ID: LibreOffice 5.2.3.3 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
Created attachment 128738 [details] Crash file
Reprdouced wtih 5.2.3.3 and 4.1.0.4 / Windows 7. Spreadsheet takes quite long to open. I tried deleting column B, a merged column. Memory usage started rising rapidly, and at around 1.6 GB LibreOffice crashed.
** 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
reproduce with, but no crash Version: 5.3.1.2 Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Layout Engine: new; Locale: nl-BE (en_US.UTF-8); Calc: group Spreadsheet opens normal. I tried deleting column B, a merged column. Memory usage started rising rapidly, 6.5GB and freezing the system. Have to kill the application and with Version: 6.0.0.0.alpha1+ Build ID: 831dca83f073bca9ad6242f1b96183eb4a49af69 CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-11-15_00:06:28 Locale: nl-BE (en_US.UTF-8); Calc: group also using all ram and swapping a lot. Needed to kill the application to.
Bug not reproducible in version Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
Dear Yasin Eyigun, 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
test in LO 6.4.1.2-x64 windows 10 64bit columns like B has Size B1:B1048576 by nearly 30.000 real lines so the area of cells is unnecessary great. no crash with delete D, than undo, and then crash with delete column B, so i made a test with file saved as ods. first delete od column d no problem next run fatal crash with delete column B.
fatal error message in 6.4.1.2 "could not create system"
Created attachment 158529 [details] ods save of xlsx-file in 6.4.1.2 great internal file with more than 1000.000 lines but only about 30.000 real lines. Reduktion to real smaller cell area can produce better result without crash.
improvement from 6.3.5.2 to 6.4.1.2 faster first load of file as xlsx and ods
in columns A B C and F are problems
in excel 2016 data of column B are the column with netbios name and more in LO 6.4.1.2 x64 in win 10 x64 data of column A are the column with netbios name and more and with target column B the line numbers are colored
Created attachment 158530 [details] save old xlsx file in newer actual Excel-2016 xlsx Status 2020 save old xlsx file in newer actual Excel-2016 xlsx Status of updates 2020
Created attachment 158531 [details] ods save of xlsx-file of newer excel 2016 in 6.4.1.2 size is more in relation to save of first xlsx save in LO 6.4.1.2 size of newer xlsx of excel 2016 is smaller than the first crash file of xlsx
with reduced file to 5120 lines delete column B fatal message of LO 6.4.1.2 could not create system bitmap! file with only 4096 lines delete of column B is ok
Created attachment 158534 [details] newer actual Excel-2016 xlsx reduced 5120 lines delete of column b fatal message LO 6.4 could not create system bitmap!
Created attachment 158535 [details] newer actual Excel-2016 xlsx reduced 4096 lines no crash with 4096 lines with delete column B so the limit is between 4096 and 5120 lines of this action in file for create system bitmap!
limit is in files between 4928 and 4960 lines. 4928 lines are ok after delete column b 4960 lines are too much. fatal message could not create system bitmap!
Created attachment 158552 [details] newer actual Excel-2016 xlsx reduced 4944 lines 4944 lines other are deleted in excel 2016 before. delete column B in LO 6.4.1.2 crash without message. with 4960 lines the crash is with message can not create system bitmap with 4920 lines no crash, all ok
Created attachment 158554 [details] newer actual Excel-2016 xlsx reduced 4930 lines here 4930 lines other are deleted in excel 2016 before. delete column B in LO 6.4.1.2 warm crash without message. LO windows long frozen. some pixels on down border. 4932 lines crash without message, LO windows go down. 4944 lines same like 4932 with 4948 lines the crash is with message window can not create system bitmap! with 4929 lines no crash, all ok
repro 7.0.0.0beta2 x64 in win 10 x64
@paulystefan@web.de: You are making a lot of tests but writing it wrong, as your notes, instead of comment for others. Please don't, you are making bug hardly readable. Instead, do all tests you want and then write a single clear comment. I lower the importance because XLSX is specific per comment 9 and MSO 2016 opens it very long, with final error.
deletion of row works for me with crash file and newer mso 2016 file Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL
Repro in 7.2+, Writer is slow and not responding for a while after column delete. That's the same as in 6.4, only we need to wait.
I tryied to delen a Column B in the Crash file and got a crash really in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 2934472ab888ebfe64a153984af2902fac63a7a0 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Unfortunately, still repro
Dear Yasin Eyigun, 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
Got a crash report: - https://crashreport.libreoffice.org/stats/crash_details/61d41f26-7607-48b6-87d5-fcab2dbc0f6d All I did was: 0. Open "Crash file" = attachment 128738 [details]. 1. Select column B. 2. Right-Click > Delete Columns. LibreOffice sat there for a ~15 seconds, using a full CPU, then just closed itself.