Created attachment 76715 [details]
gdb full backtrace
When saving an extremly large spreadsheet, LibreOffice dies for me with SIGABRT. Its not related to memory shortage, as LibreOffice consumes only about 1.8gb of RAM while my machine has 8GB and is running Linux-64 with LibreOffice 64-bit binaries.
Steps to reproduce:
1. Download the file at: https://mega.co.nz/#!5d0j3b6A!chMGwxtsd3qKHPPkWKOrDlryAFtaZrI91dUiuQ3Jva4
2. Open the file
3. Modify a single cell somewhere
4. Press Ctrl+S to save the file again
Could you please send us the doc with an other way ? http://dl.free.fr/ for example
Created attachment 78107 [details]
Log trace without crash
Can't reproduce the crash for now but seems to have some leaks.
Thanks for reporting.
I can confirm this documents keep filling my memory (now up to 3,5GB of the total 4GB (92,0%), and raising). So therefore we can mark this bug as NEW and accept the bug report.
On the other hand, this bug may be never get fixed. The only thing we can advice is to try to use a database instead of such extremely huge documenst (159mb of information). A spreadsheet isn't meant to manage such kind of data; a database is.
I hope you understand.
> On the other hand, this bug may be never get fixed. The only thing we can
> advice is to try to use a database instead of such extremely huge documenst
> (159mb of information).
Memory leaks typically are not related to the size of the data, therefore calc probably leaks also with smaller documents, which definitively is a bug and has to be fixed.
> A spreadsheet isn't meant to manage such kind of data;
> a database is.
Probably, probably not. Excel-2013 has no problems with spreadsheets of such size and loads the xsls-version of the same document consuming far leass than 1GB of memory. In my opinion that should be reason enough to fix calc to make it equal to its competitor...
Adding self to CC if not already on
Migrating Whiteboard tags to Keywords: (perf)
** 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.1.6 or 5.2.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)
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!
example file was removed from site on link
retest of this bug is impossible
Xisco, what I should make with this situation?
cool I filed this bug-report almost 6 years ago ;)
(In reply to Clemens Eisserer from comment #10)
> cool I filed this bug-report almost 6 years ago ;)
can you retest your problem with latest version of LO 6.1.3 or current dev-buid 6.2 or 6.3?
Dear Clemens Eisserer,
OTOH, please provide the document to reproduce the issue...
I am sorry, but I don't have the document any more. I didn't think this bug would stay essentially un-looked at for 6 years.
Unfortunately there's not much we can't do if the document is not available anymore...
Closing as RESOLVED INSUFFICIENTDATA.