Created attachment 117890 [details] crash popup message This bug was reported by my customer for LibO Calc 5.0.0.5 on MS Windows platform. I tested it in a daily build 5.1.0.0.alpha1+ Build ID: 9ef671364ff9fbb552a5433053af9283d12d90c7 on Linux platform, and it seems to be reproducible there as well. I saw increasing memory usage by soffice process, using 'ps' tool. My customer reports that LibO crashes when all memory goes away, reporting an com.sun.star.uno.RuntimeException, screen shot attached I tested on Version: 4.4.5.2 Build ID: 4.4.5.2 Arch Linux build-1 and I do _not_ observe the issue there (ps command doesn't show that memory usage by soffice increases). Steps to reproduce: 1. Launch LibO calc 2. create following macro: Sub Main Sheet = thisComponent.Sheets("Sheet1") For i =0 to 10000000 dann ="42202705" Sheet.getCellByPosition(0, 0).String = dann & " i=" & i Next i End Sub 3. run the macro 4. observe memory usage with ps -aef |grep soffice in some time RAM goes out and LibO crashes
These bugs may be related: #88006 #93392
My customer says that the issue is _not_ reproducible in OpenOffice 4.1.1 on MS Windows
I can not confirm with Version: 5.1.0.0.alpha1+ Build ID: 6b7354ae66db40246a09e00aa876443057655a43 TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-08-19_01:05:16 After ~3 hours of run macro ended without crash, "42202705 i=10000000"
But soffice takes 50% of memory (6GB of RAM)
I didn't saw the crash on LibO 5.1 master branch either, just increasing memory usage. Did you test with patch for https://bugs.documentfoundation.org/show_bug.cgi?id=93392 integrated? I feel it may fix the issue.
Hm, I see from source code that the fix for #93392 does not affect current case, it's for HTML parsing. And I tested against the latest /daily/master/Linux-rpm_deb-x86_64@70-TDF-dbg/2015-08-21_07.14.55 and it behavior remains the same.
** 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.5 or 5.2.1 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I can't reproduce this leak with current master on Linux.
Mikhail/Raal: following Noel's comment, do you reproduce the memory leak with 6.1.3?
Yes, the issue still reproduces in LibO 6.1.3.2 - running macro eats RAM indefinitely.
Version: 6.1.3.2 Build ID: 6.1.3-1 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group threaded From Arch Linux distro
Dear Mikhail Zemlyanukha, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Mikhail Zemlyanukha, 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
Does not seem to be present on macOS Version: 24.8.4.2 (AARCH64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 8; OS: macOS 15.2; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Real Memory Size reported by Activity Monitor: Open LO no windows open: 1.15 GB Create new spreadheet window: 1.19 GB Create macro: 1.23 GB Macro running: 1.30 GB (i=0) Macro running: 1.25 GB (i=13000) Macro running: 1.32 GB (i=30000) Macro running:s: 1.27 GB (i=335000) [After 5 hours of running] It does seem to me that the macro runs rather slowly but that is presumably because it updates the displayed value of the cell every time.