Description: Tracking changes pasting to multiple columns generates uses > 5 GB ram (without undo steps) and takes far to long Steps to Reproduce: 1. Open Calc 2. Tools -> Options -> Advanced -> Expert configuration -> Search for Undo Reduce 100 to 0 3. Close & restart 4. Open the attached file 5. Enable tracking changes 6. Copy A1 7. Select column A until W 8. Paste Actual Results: A memory consuming process starts Expected Results: Undo needs 800 MB; so tracking changes does something wrong Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 83c4f86f22dc37269ac6a038fe7de053c42aad6e CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL
Created attachment 161456 [details] Example file
may - again - be win-only, mem usage with below ver. moderate, ~800M, Version: 7.0.0.0.alpha1 Build ID: 6a03b2a54143a9bc0c6d4c7f1... CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: de-DE (en_US.UTF-8); UI: en-US Calc: threaded
(In reply to b. from comment #2) > may - again - be win-only, > > mem usage with below ver. moderate, ~800M, > > Version: 7.0.0.0.alpha1 > Build ID: 6a03b2a54143a9bc0c6d4c7f1... > CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; > Locale: de-DE (en_US.UTF-8); UI: en-US > Calc: threaded Sounds odd to me I do reproduce this also with Version: 6.4.3.2 Build ID: libreoffice-6.4.3.2-snap1 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded 800 sounds more like normal paste ... without tracking changes enabled..
@Telesto: > 800 sounds more like normal paste ... without tracking changes enabled.. maybe you are right ... on the one hand i'd have sworn i've seen the notes indicating time and change on mouseover, on the other hand a retest yesterday with below ver. on another machine sucked all 10.5 GB of available mem and then (k|gr)illed my usb-port! heavy load still pasting (machine started swapping? it had no swap partition defined), sudden freeze of mouse, keyboard and desktop, usb port unusable after reboot, setting to new, but won't do further tests 'til machine is repaired ... :-( Version: 7.1.0.0.alpha0+ Build ID: a0c90f1bccd9b5a349d3199746facab549f27dba CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.utf8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-06-01_02:36:12 Calc: threaded P.S. for those who find this thread searching for usb problems, or if someone has a tip for the port: machine Lenovo P70 xeon, fresh OS running from a live usb-stick (kali 2020.2), port on the left side, the port is grilled, not the stick (sandisk ultra-fit 256GB), stick still works on other ports, port doesn't recognize any of my devices anymore,
Should have used a smaller example.. I was aware of the possible freeze. I mostly killed the process before it did..
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