Created attachment 125159 [details] CSV file used to reproduce the problem When calculating a moving average for the attached CSV file, libreoffice uses 100% CPU, and uses increasing amounts of memory until I kill it. Steps to reproduce: 1) Open the attached CSV file 2) Select both columns 3) Data -> Statistics -> Moving Average - Input range should be `$scores2.$A$1:$B$1048576` - Results To should be `$C$1` - Grouped by columns - Interval 20 Clicking OK will then cause 100% CPU usage on one core, and gradually more memory usage. It managed to take 10 minutes on my machine and use 2GB of RAM before I killed it. If I select only the 142 rows of data then it calculates it almost instantly. Expected behaviour: The average should ignore the empty rows, and give a result as swiftly as just selecting the top 142. Libreoffice Version: LibreOffice 5.1.3.2 10m0(Build:2) Operating System: Arch Linux Kernel: Linux 4.5.4-1-ARCH x86_64
Hi @Robert, thanks for reporting. Reproducible. Version: 5.1.3.2 (x64) Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Version: 5.0.6.2 (x64) Build ID: b3fbfa99158a1030fb79f0ba72b6851afc3c7895-GL Version: 4.2.8.2
** 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.2.7 or 5.3.3 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-20170522
Still reproducible: Version: 5.3.3.2 Build ID: 5.3.3-1 CPU Threads: 4; OS Version: Linux 4.10; UI Render: default; VCL: gtk3; Layout Engine: new;
Still Version: 5.3.3.2 (x64) Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new; Locale: es-ES (es_ES); Calc: group
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this. Alex: could you give a try with XCode memory analyzer? (BTW, about this tool, which tuto have you used?)
** 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 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 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: 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
Still reproducible in master (HEAD=09b9499de17991bbd6b808c0c7923fda6e616e79). I'll try to fix it.
Dennis Francis committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/2fd8f56ed1bf9b547093c4ac6c3231fff001b748%5E%21 tdf#99938 : Moving Average : By default trim input range... It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Dennis Francis committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/1bfbe2a44021ca4ae6716caa39fc8a375914be5c%5E%21 tdf#99938 : Allow batch of formula-cells to be written... It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Now there is a checkbox for "Trim input range to actual data content" (checked by default) in the moving average dialog. The underlying cause for slowness was also mitigated to some extend, so even without this new checkbox checked, the computation for the $A$1:$B$1048576 range as said in the reproduction steps finishes in a few seconds.
(In reply to Dennis Francis from comment #10) > Now there is a checkbox for "Trim input range to actual data content" > (checked by default) in the moving average dialog. The underlying cause for > slowness was also mitigated to some extend, so even without this new > checkbox checked, the computation for the $A$1:$B$1048576 range as said in > the reproduction steps finishes in a few seconds. Dennis, thank you for fix. Can you please write about this changing in to Release Notes 6.3 in our wiki?
(In reply to Roman Kuznetsov from comment #11) > (In reply to Dennis Francis from comment #10) > > Now there is a checkbox for "Trim input range to actual data content" > > (checked by default) in the moving average dialog. The underlying cause for > > slowness was also mitigated to some extend, so even without this new > > checkbox checked, the computation for the $A$1:$B$1048576 range as said in > > the reproduction steps finishes in a few seconds. > > Dennis, thank you for fix. Can you please write about this changing in to > Release Notes 6.3 in our wiki? Done.