Description: Excessive memory consumption when I try to run RaytracerInExcel_CopyFormulae.xlsb from https://github.com/s0lly/Raytracer-In-Excel Excel 2019 runs this with approximately 850 megabytes of memory Libreoffice calc used 7 gigabytes Steps to Reproduce: 1. Download file from https://github.com/s0lly/Raytracer-In-Excel/raw/master/RaytracerInExcel_CopyFormulae.xlsb 2. open file. 3. Open objects tab. 4. copy Row 24 in the "Objects" tab, and paste it on to Row 25 to Row 14405 inclusively Actual Results: Libreoffice used 7 gigabytes of memory. Expected Results: Libreoffice uses 800 megabytes of memory Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Skia is enabled
Created attachment 177312 [details] Xlsb file
I confirm the memory leak in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1be170d0629cf761f0ee4173007a3c021966546e CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL and in Version: 5.2.7.2 Build ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: ru-RU (ru_RU); Calc: group
I can't find from where the 800 expected comes. Only opening the file, about 585 MB. After paste and after a while it is reduced to 2,5 GB, without touch nothing. After a hard recalc 1,7 GB, takes several minutes. So I don't know if it is really a bug or a possibility of enhancement. BTW, there are a lot of formulae with OFFSET() which is a volatile function, maybe where possible replace it with INDEX() could help a bit on the calculation's speed, and perhaps SUM() in arrays with SUMPRODUCT().
Memory leak still here and it became even worse becasue we have today 16384 columns on sheet by default Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 9d1d668a608cc5b406601c2f7f3d8581e8f47d1c CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded
Dear Кирилл Фролов, 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
Still repro in Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0a004f1a1528b8a85245de4672852b574bdc2cb2 CPU threads: 16; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded