[Libreoffice-bugs] [Bug 82143] VIEWING: 100% CPU while Scrolling a specific document

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Michael Stahl <***@redhat.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #104110|application/octet-stream |text/plain
mime type| |

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Robinson Tryon (qubit) <***@runcibility.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |filter:odt, perf
CC| |***@runcibility.com
Whiteboard|BSA perf filter:odt |BSA

--- Comment #9 from Robinson Tryon (qubit) <***@runcibility.com> ---
Migrating Whiteboard tags to Keywords: (filter:odt, perf)

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #10 from QA Administrators <qa-***@libreoffice.org> ---
** 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.6 or 5.2.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-20170103

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #11 from Volga <***@outlook.com> ---
Yousuf Philips, what happened when you try it on a machine with multi
core/thread CPU?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #12 from Volga <***@outlook.com> ---
Also, what about GPU?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Yousuf Philips (jay) <***@hotmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@caesar.elte.hu,
| |***@suomi24.fi,
| |***@libreoffice.org

--- Comment #13 from Yousuf Philips (jay) <***@hotmail.com> ---
(In reply to Volga from comment #11)

Post by b***@bugs.documentfoundation.org
Yousuf Philips, what happened when you try it on a machine with multi
core/thread CPU?

The CPU i tested on had 2 cores/threads, which is why the overall CPU hit 50%,
meaning one of the CPU cores/threads was at 100%.

I tested a recent build and there are still freezing issues when the document
loads and then my entire system seems to freeze when i scroll to around page 7
or so.

Version: 5.3.0.1.0+
Build ID: d1b8074ffe4b945a41e3ad9e1fb43332d78d73fb
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; VCL: gtk2; Layout
Engine: new;
TinderBox: Linux-rpm_deb-***@70-TDF, Branch:libreoffice-5-3, Time:
2017-01-10_23:02:10
Locale: en-US (en_US.UTF-8); Calc: group

Opened the doc with Calligra Words and after a few minutes of loading and a CPU
core at 100%, the document was viewable and scrollable without problems.

@Xisco, @Aron, @Bouvjaga: I've shared the document with you guys privately on
google docs for testing. Initially i thought images may be causing the issue,
but deleting all the images from the doc still didnt solve the issue.

@Meeks: Document also shared with you privately on google docs, so does a
valgrind or callgrind need to be done on the doc to find out where the problem
is?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #14 from Aron Budea <***@caesar.elte.hu> ---
(In reply to Yousuf Philips (jay) from comment #13)

Post by b***@bugs.documentfoundation.org
I tested a recent build and there are still freezing issues when the
document loads and then my entire system seems to freeze when i scroll to
around page 7 or so.

I see dynamic-cast-related code taking up a lot of runtime, and the execution
going in a neverending circle into/inside of:
const SdrObject *SwOrderIter::Next()

The dynamic casts are this:
if ( m_bFlysOnly && dynamic_cast<const SwVirtFlyDrawObj*>( pObj) == nullptr )
http://opengrok.libreoffice.org/xref/core/sw/source/core/layout/frmtool.cxx#2219

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #15 from ***@gmail.com ---
Hi, I'm having the same problem, is there a workaround for this?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Yousuf Philips (jay) <***@hotmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |haveBacktrace
Blocks| |113510


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113510
[Bug 113510] [META] Bugs that cause CPU to run at 100%

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #16 from Marc Schipperheyn <***@gmail.com> ---
I see the same behavior making working with LibreOffice a bit of a nighthmare

Version: 6.3.2
Document type: Microsoft Word docx with comments. No images
Computer: MBP2018 15 inch

With openGL disabled
- scrolling speed is perhaps 50fps. It's workable but not smooth, the scrolling
is a bit janky.

with openGL enabled
- scrolling speed is perhaps 30fps. choppy. with the screen catching up all the
time to the scrolling intent

Neither is acceptable.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #17 from Marc Schipperheyn <***@gmail.com> ---
That should be version: 6.1.3.2

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Telesto <***@surfxs.nl> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords|filter:odt |bibisectRequest,
| |filter:docx, regression
Status|NEEDINFO |NEW
Version|Inherited From OOo |6.3.0.0.alpha0+ Master

--- Comment #21 from Telesto <***@surfxs.nl> ---
Tested sample1.docx

Repro with
Version: 6.3.0.0.alpha0+
Build ID: beae6c7a7f163daad0d4dea63a3d403af2745fd1
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win;
TinderBox: Win-***@42, Branch:master, Time: 2018-12-06_23:55:16
Locale: en-US (nl_NL); UI-Language: en-US
Calc: CL

but not with
Versie: 4.4.7.2
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #22 from Buovjaga <***@suomi24.fi> ---
(In reply to Telesto from comment #21)

Post by b***@bugs.documentfoundation.org
Tested sample1.docx
Repro with
Version: 6.3.0.0.alpha0+
Build ID: beae6c7a7f163daad0d4dea63a3d403af2745fd1
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win;
Locale: en-US (nl_NL); UI-Language: en-US
Calc: CL
but not with
Versie: 4.4.7.2
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

Just so we don't forget: now we are no longer dealing with the original issue
that was seen in 3.3.0 already.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #23 from Jean-Baptiste Faure <***@libreoffice.org> ---
(In reply to Buovjaga from comment #22)

Post by b***@bugs.documentfoundation.org
[...]
Just so we don't forget: now we are no longer dealing with the original
issue that was seen in 3.3.0 already.

Indeed, so to make things clear, we should close this bug report as
InsufficientData and open a new bug report with the test file provided in
comment #20.

Best regards. JBF

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #24 from Buovjaga <***@suomi24.fi> ---
(In reply to Jean-Baptiste Faure from comment #23)

Post by b***@bugs.documentfoundation.org
(In reply to Buovjaga from comment #22)

Post by b***@bugs.documentfoundation.org
[...]
Just so we don't forget: now we are no longer dealing with the original
issue that was seen in 3.3.0 already.

Indeed, so to make things clear, we should close this bug report as
InsufficientData and open a new bug report with the test file provided in
comment #20.

I recommend doing the bibisect first, then searching with the hash for a
previously reported issue. Maybe it has already been reported.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #18 from Jean-Baptiste Faure <***@libreoffice.org> ---
Well, without a public test file, I think this bug report is completely
useless. Each tester can put whatever he want behind "specific document" and it
is impossible to know if the problem has the same root cause than the firstly
reported. Nothing can be done with a private document if it is not in the hands
of a developer.

Best regards. JBF

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

Xisco Faulí <***@libreoffice.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO

--- Comment #19 from Xisco Faulí <***@libreoffice.org> ---
(In reply to Jean-Baptiste Faure from comment #18)

Post by b***@bugs.documentfoundation.org
Well, without a public test file, I think this bug report is completely
useless. Each tester can put whatever he want behind "specific document" and
it is impossible to know if the problem has the same root cause than the
firstly reported. Nothing can be done with a private document if it is not
in the hands of a developer.
Best regards. JBF

I agree!
@Johannes Nickel, Please provide a sample document to reproduce this issue...

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=82143

--- Comment #20 from George Sofianos <***@gmail.com> ---
Created attachment 147417
--> https://bugs.documentfoundation.org/attachment.cgi?id=147417&action=edit
Sample documents

I'm attaching some sample documents. At the moment sample1 is freezing my
libreoffice writer when scrolling, but it might depend on the CPU.

Please delete the sample when this is done