https://bugs.documentfoundation.org/show_bug.cgi?id=129121
Bug ID: 129121
Summary: Big mod to big spreadsheet: FILESAVE Bad Allocation
crash
Product: LibreOffice
Version: 6.1.5.2 release
Hardware: x86 (IA32)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: mwh...@mail.com
Description:
Performing a large operation (such as selecting and copying and pasting
thousands of rows from one worksheet into another worksheet) in a large Calc
spreadsheet will seem to work fine but will lead to a Bad Allocation crash when
attempting to save the modified spreadsheet. The attached files demonstrate the
problem.
Steps to Reproduce:
1. Using attached file ProblemDemo.ods, go to the sheet named Orig Price Data
2. Enter cntl-A to select the entire sheet (~4000 records in use)
3. Enter cntl-C to copy the entire sheet
4. Go to the blank sheet named Pared Price Data
5. Enter cntl-V to save all copied data
6. Enter cntl-S to save the entire spreadsheet to disk
7. Wait while this operation proceeds: takes many minutes on my little Acer
8. When the Bad Allocation error occurs, click on OK and watch Calc crash
Actual Results:
Calc exits memory. The next time it is used, it asks if you wish to restore the
above file, but nothing is there to be restored, so you are right back where
you started -- all of your extensive changes are gone.
Expected Results:
It should save the file properly, of course.
If that is somehow impossible, it should at least warn you and continue running
so that you have a chance to copy your changes (perhaps just one or two of many
worksheets) to a different file.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
I am seeing this problem A LOT over the past few days (since 25 November 2019).
I have two large files that I can send to you that should help in isolating the
problem. I will attach them to this form.
One of the files is a text version of the Windows 10 System Information (about
0.8 Mbytes) so you can see the specifications of my computer and the Windows 10
version number and all of those things. The other file is an actual spreadsheet
file (.ods file) that causes the problem very consistently. It is about 26
Mbytes.
I have spent a lot of time using LibreOffice Calc over the past few years.
About nine months ago I installed LibreOffice 6.1.5 and used it up until this
week creating a dozen or so *large* spreadsheets with file sizes of 180 Mbytes
or more. These are slow to load and slow to save, but other than that they
*had* been working fine. Suddenly that all changed this week. I cannot seem to
do the simplest operation in any of those large files without getting a Bad
Allocation error message when I try to save my changes.
I started all over on a new file and gradually built it up to be very much like
my other files. When it reached about 20 Mbytes in size, I started getting the
Bad Allocation error. It has lots of tabs (lots of sheets) but in particular it
has two named Orig Historical Price Data and Orig Historical Cap Data. The
first of these two contains almost 4000 records. I would like the second of
these two to be an exact copy of the first (as a starting point for my work).
However, I can only copy a few hundred records from one to the other and still
save the changes. If I copy thousands of records from one to the other, then I
get a Bad Allocation message when I try to save the changes.
I tried running in Safe Mode (as recommended in "instructions for resolving
User Profile corruption" and the problem still happened.
I tried running with OpenGL disabled and the problem still happened.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
