1. When saving the very large spreadsheet at https://mega.co.nz/#!5d0j3b6A!chMGwxtsd3qKHPPkWKOrDlryAFtaZrI91dUiuQ3Jva4 to xsls-format, calc consumes about 3.8 GB of memory. When closing the document and working with an empty writer document, memory consumption only decreases to about 3GB. 2. Close the LibreOffice instance which was used for step 1. When opening the xsls-file generated in step 1 with a fresh libreoffice instance, calc consumes about 1.3GB of memory (which is ok). When saving the file again to xsls, memory consumtion grows to 6.8 GB. After closing the document and working a bit with writer, it stays at 5GB. Beside the really huge memory consumption, the memory used for both steps should be freed. Instead, memory consumption only decreases slightly when closing the calc window which contains the large spreadsheet.
Excel-2010 just needs 300mb of RAM after loading+saving the document generated by LibreOffice.
Markus - I'll test this one when I'm at home but I thought it might be a good test case for you (150 megs...pretty hefty file). Might have some cool stuff going on that can be used to track down performance issues.
OK, I'll add it to my list. But mainly the memory consumption after closing Calc. That the current OOXML filters are not very efficient is known and has to wait for something like the orcus implementation.
Sorry for the delay - so I confirmed enough to mark this as NEW and confirm that it's a good test case to improve our filters. IMO there are 2 problems that highlight everything else. 1. Opening the ODS itself takes up nearly 3 gigs - seems excessive for a 150 meg file 2. The memory is never freed up because of point #2, I can't confirm the save to XLS as I only have 4 gigs of RAM and 1 gig of SWAP. Markus - do you have a system with insane amount of RAM (8+ gigs?) to confirm behavior in point 1 & 2 about saving to xlsx - first time only being 1ish gigs but then after it just eating RAM alive?
** 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 (4.4.2 or later) 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
After following the steps on Debian 8 (jessie) 64 bits I've got: 1.- I opened the spreadsheet and memory goes to almost 1GB 2.- When saving to xlsx memory went onto 1,9GB and when the process finished memory got to 1,4GB 3.- After closing the document memory went to 1,2GB. Tested on: Version: 5.0.0.1 Build ID: 9a0b23dd0ab9652e0965484934309f2d49a7758e Locale: es-ES (es_ES.UTF-8)
Migrating Whiteboard tags to Keywords: (perf)
The test file has been removed
Hi Clemens, Could you please upload the document again ?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180102
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180129