Description: After much investigation I realised that the structure of the file itself is part of the problem. If I copy paste the file in a standard text editor and paste it back into LO it works without issue. I can't seem to figure out what's the problem with the file structure itself someone with more knowledge will have to continue. I have tried all version from 5.1.x to 5.4.x and they all have the same problem. The slow down seem to be different when editing different place in the file but right at the beginning is a good example. The hardware should not be a problem as it is on a recent quad core machine. Steps to Reproduce: 1. Open attached file 2. Edit document at the beginning of file 3. Actual Results: Lag and latency above what I would consider normal Expected Results: No perceived latency when editing Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Created attachment 138476 [details] Test file exhibiting the slow down problem
For reference this was on Ubuntu 16.04.
Confirming the slowness (and high CPU usage) Version: 6.1.0.0.alpha0+ Build ID: aad9c6da5154a89c6ef02214d1122d4b444eea23 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-12-15_22:56:44 Locale: nl-NL (nl_NL); Calc: CL Fast but still high CPU usage with: LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Copy/Pasting the text as unformatted text into a new document will resolve the issue
A valgrind trace would be nice ;-)
In the beginning of content.xml there is: <text:span text:style-name="T1">Le</text:span> <text:span text:style-name="T2">cture #1</text:span> <text:span text:style-name="T1">. </text:span> <text:span text:style-name="T3">This </text:span> <text:span text:style-name="T4">is is the problem </text:span> <text:span text:style-name="T5">with the problem</text:span>
Created attachment 139993 [details] Callgrind output from master First deleted some text and then typed to another location in the beginning (with the split spans). Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: c902cbc7dc5294ab721a9aef3a152aa243d00011 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on February 17th 2018
@Khaled Would you mind to take a short peek at the callgrind trace. It looks quite a lot like bug 112989. However, existing already before Harfbuzz. Thanks!
It is a well known fact that our text layout performance is sub-optimal; the code was written long ago with the assumption that text layout is cheap and can be re-done whenever needed, but that is not the case any more and and overhaul is long over due. I’m pretty sure this was mentioned before somewhere.
Created attachment 140009 [details] Screenshot (In reply to Khaled Hosny from comment #8) > It is a well known fact that our text layout performance is sub-optimal; the > code was written long ago with the assumption that text layout is cheap and > can be re-done whenever needed, but that is not the case any more and and > overhaul is long over due. I’m pretty sure this was mentioned before > somewhere. You did.. Should have been more specific with my question. Sorry! I'm not quite sure if this is really about the text layout at all. Could be more or less unrelated. The main problem could be segmentation fault: I'm noticing _dl_runtime_resolve_xsave'2 (I have add a screenshot) Anyway thanks for the quick response!
(In reply to Buovjaga from comment #5) > In the beginning of content.xml there is: > > <text:span text:style-name="T1">Le</text:span> > <text:span text:style-name="T2">cture #1</text:span> > <text:span text:style-name="T1">. </text:span> > <text:span text:style-name="T3">This </text:span> > <text:span text:style-name="T4">is is the problem </text:span> > <text:span text:style-name="T5">with the problem</text:span> Redundant styles, but I think real issue is that those styles are not defined in styles.xml. Saw similar in attachment 120477 [details] from Bug 95633. I wonder how those docs were created (probably wrong, by formatted copying). Guess Writer is checking back and forth in vain. So if I understand this, we may wait for an overhaul or do something if styles are not defined.
Dear lotusom-dev, 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
This bug is still present now under Ubuntu 18.04 LTS and LibreOffice version Version: 6.2.5.2 Build ID: 1:6.2.5-0ubuntu0.18.04.1~lo1 However, I had not look at the time at the file of bug 95633 discussed in comment #10 but the problem is much more noticeable in this file.
Dear LotusDev, 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
I tested this now under 7.1.5.2 and the bug is no longer present, we can close this.