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.
Hi, 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. Kind regards, Joren
Hi. > 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
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.