If I delete a long word with the backspace key, the cpu rises up du 13% and the green "progress bar" down in the status line is visible for a secound or so. The process is slow (much slower than tiping the same amount of letters). The document is around 60 pages but with a lot of formulas (~200). Is this a known "problem"? Tested with 220.127.116.11 and 18.104.22.168
Thank you very much for your work on this great piece of software!
Thank you for reporting the bug. You're probably on to something (I did a quick test with quite different document). Please attach a sample document. So I can check if it's the same bug.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it.
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 136936 [details]
Hi, thank you for your fast answer!
I have an idea of the "bug": It is due to the "change log". If the changes are visible, everything is very fast and responsive - works like a charm. But if the changes are hidden (while recording the changes), the deletion of a letter is slow and costs "a lot" of CPU power...
Sorry, I didn't know, that I was recording the changes and it tooks me 2 hours to reproduce the problem with a fresh document... But here it is...
Thank you all for your phenomenal work on LibreOffice!
I used the attached document. That’s right when using back space to delete or undo button the CPU utilization jump from 2 % to 30 % and more. Even I tried to reproduce the issue with two other different files, I got the same situation.
Test environment :
• Operating system : Windows 8.1 Pro 64-bits.
• LibreOffice : Version: 22.214.171.124
Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU threads: 4; OS: Windows 6.2; UI render: default;
Locale: en-US (en_US); Calc: group
NEW per comment 3.
Build ID: b3f1d199a72ce87cb65ddaeac922564f57da6a4d
CPU threads: 4; OS: Windows 6.3; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-11-06_00:10:53
Locale: nl-NL (nl_NL); Calc: CL
Versie 126.96.36.199 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
No repro without tracking changes enabled/recording
Probably a dupe
(In reply to Telesto from comment #5)
> Repro with
> Version: 188.8.131.52.alpha1+
> Build ID: b3f1d199a72ce87cb65ddaeac922564f57da6a4d
> CPU threads: 4; OS: Windows 6.3; UI render: default;
> TinderBox: Win-x86@42, Branch:master, Time: 2017-11-06_00:10:53
> Locale: nl-NL (nl_NL); Calc: CL
> and with
> Versie 184.108.40.206 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
> No repro without tracking changes enabled/recording
> Probably a dupe
what's a dupe?
Created attachment 144321 [details]
I made a video of my 4 CPU working hard in deleting some letters on 6.2
Build ID: f05b0a6aaf8af5d78f9cad8bb953228cb0ce09f1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-08-20_01:57:14
Locale: ro-RO (ro_RO.UTF-8); Calc: threaded
Created attachment 144322 [details]
I created a new file with just the text "test". 35 pages... This is the file I tested it.
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!
Version: 220.127.116.11.alpha0+ (x64)
Build ID: 42a1a1c6b91907f81e15066ffab219411f18c4db
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US