Created attachment 157017 [details] spreadsheet to generate the spreadsheet making troubles using the attached spreadsheet I created a huge spreadsheet executing the 2 commands in line 3 of table _Tabelle2_ . Saving this file is possible in format xlsx and ods. Loading the saved file without error is only possible in format xlsx but not in format ods. To handle the file you will need 16GB RAM . Using Ubuntu 18.04 (LibreOffice 6.0.7.3) I can save the created file without error only in format xlsx but not in format ods.
The problem starts before one can load the generated file: steps to reproduce: - open attached file - select "Tabelle2" - select cell range "A9:X373256" - press ctrl + D LO crashed with a "Bad Allocation Error" on my Win 10 x64 Notebook (8GB RAM) after "soffice.bin" grows up to ~ 4,3GB. Notebook gets instable, e.g. Firefox browser crashed, screen went black.
(In reply to johannes.geest from comment #0) > Loading the saved file without error is only possible in format xlsx but > not in format ods. To handle the file you will need 16GB RAM . With a different Notebook (Win 10 x64, Core i7 32GB RAM) i was able to generate the data. It took ~ 10 minutes and "soffice.bin" was ~ 10GB. The *.tmp file grew up to 5GB, saving *.ods took ~10 minutes, file size 170 MB. Loading *.ods will fail wih an error - did not try to save as *xlsx.
Dear johannes.geest, 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
So (here is Intel Core 2 Quad 9450 with 8 Gb of memory): I had 100% CPU loaded of one CPU core and allocated over 5 Gb of memory after Ctrl+D pressing. Time for (never) ending is around 25 minutes and then I killed the process. I didn't have the crash in this case. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1be170d0629cf761f0ee4173007a3c021966546e CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL
This is at least partially bug #129892. The uncompressed xml content is larger than 4GiB, we don't support zip64, and ZipOutputStream::writeEXT() throws.