Description: Sheet from file based on CSV uses 50% more compared to direct opening of the file Steps to Reproduce: 1. Open Calc 2. Sheet -> Sheet from file 3. Download and unzip attachment 161733 [details] 4. Open the file 5. Press OK Actual Results: 1469 MB needed with peak to 1900 MB Expected Results: Directly opening CSV uses 900 MB (still to much, but an improvement already) Opening same content from ODS uses 350 MB (except if saved from CSV import; bug 133759) Reproducible: Always User Profile Reset: No Additional Info: Found in 7.1 and in Version: 4.1.0.0.alpha1+ Build ID: 863d38fbfa4fb4861e476828c46410602100919
I confirm and it is a bit unexpected. It is not dependent on undo, happening with 0 undo steps as well. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 9b34dc20b6946698ae6ce2d5d859885bfb444633 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 16 October 2020
https://www.phoronix.com/forums/forum/software/desktop-linux/1228246-libreoffice-7-1-rc1-released-for-testing-this-open-source-office-suite?p=1228257#post1228257 I just wish Calc would get a bit more powerful. It craps out on my system with 64GB of memory when trying to sort large imported csv files. I always have to boot into Windows and use Excel for that.. which is nasty.
@Michael As you do care about Calc bugs (or I'm widening the scope, I it was only about Calculations) Anyhow not sure how often CSV import is used in Enterprise setups for large chucks of data, say 10 mb csv data. If that's the case, which kind guess happens this should be addressed The ram usage kind of explosive and the performance is also affected by it. Looks like duplication (or maybe even triple) of data somewhere). Reason for the nudge: comment 2. Kind of seeing this a low hanging fruit, as I estimate is relative simple to solve [but well my estimates are not reliable at all] Only putting it on the radar; can't asses the Enterprise demand
Dear Telesto, 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