Created attachment 68948 [details] Test File Steps to Reproduce: Open included TestFile, click into text in the right column (second row). Keep press down arrow and move to the end of document. Keep press up arrow and move on the top of document. Actual Results: While moving up hang for a several minutes in the middle of document - see included movie. Expected Results: Moving through document without any hangs. Additional Information: My Computer: iMac i5(3,1GHz), 12GB RAM, Mac OS X 10.7.5. There appear bad formated area without any specific reason - see screenshot. I've attach some sample of process. I cannot reproduce it in LO 3.5.7, but everytime on 3.6.x Workaround: No.
Created attachment 68950 [details] Sample of process
Created attachment 68951 [details] Screenshot of bad formated area
Created attachment 68952 [details] Screen record - for playback use VLC (quality is poor due filesize limit :-) )
Comment on attachment 68948 [details] Test File (Fixed MIME type.)
Thank you very much for your bug report! I can reproduce the delay with LibreOffice 3.6.3.1 (on Mac OS X 10.6.8 Intel) when scrolling (by pressing the down arrow) through the right column of your sample document; and indeed, the delay is *really* long and *really* annoying, I completely agree to you. However, my first tests showed two differences to your report: 1 When I have scrolled once comletely through the document (and back), further attempts to scroll through the document in the same way work much faster -- no delay anymore (?). The delay returns when I close the document and open it again. 2 When testing the same with LibreOffice 3.5.7.1, I get a long delay, too, at least at one point (IIRC the same strangely formatted area which is shown on your screenshot, attachment 68951 [details]). Maybe this delay is not as long as in 3.6.3.1, but there *is* such a delay, of course. Maybe I did something wrong in testing. But could you please check yourself if you can share my observations, or if there is really a difference? (No offence! I just want us to check these points before confirming the bug and forwarding it to the developers, because it can be important for fixing the bug if there is really a regression [2] and if the delay appears only directly after the opening the document.) Thank you very much!
Hi Roman, 1) When I wait several minutes (~3 minutes) LO continue and after that I can scrolling through document without delay. After reopen file (without relaunch LO) delay appear again. In previous attepts I hadn't enough patience to wait :-), but it is really as you say, there is very, very long delay - so it is NOT infinite loop, but long delay. 2) I've test it on LO 3.5.7.2 (build ID: 3215f89-f603614-ab984f2-7348103-1225a5b) but this problem occure if I scroll via mouse, not via up/down arrow. So my ansver: Q: There is really a regression? A: No, but in LO 3.5 delay might occure less frequently. Q: Appear the delay only directly after the opening the document. A: Yes. After delay problem disappear until reopen the document. When the delay occure (any version of LO), always appear formating bug similar as I attach to this bug in right column text.
hang while scrolling document reproducible under Win7x64 using LibO 3.6.0.4, 4.3.2.2 and 4.4.0.0+ bug not reproducible with 3.5.7.2 and 3.6.0.4 so I confirm this very old 3.6.x regression. needs bibisecting.
Unfortunately I can reproduce this reliably all the way back to 3.3.0. Rather than a regression, this is just a really old bug. Removing Keywords:regression and Whiteboard:bibisectRequest
If you set the page view to single page and zoom out to about 60% then pages 7 and 8 have images in frames off to the right of the page. Images have their width set to a percentage that is relative to the paragraph area. Just opening the image dialogue and switching between the tabs and cancelling caused the images to appear. Existing ones will change if you go into the dialogue and switch tabs and come out. Still hangs for a few minutes. Windows Vista 64 Version: 4.4.4.3 Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8
** 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.5 or 5.2.1 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-20160920
I can confirm this bug on: Version: 5.3.0.0.alpha1+ Build ID: bb50b1609abe83265311613db4a18e992dc666c8 CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-11-14_23:25:25 Locale: nl-NL (nl_NL); Calc: CL For me scrolling down is enough.
** 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 hangs in LibO 6.0.4 did not try 6.1.x or 6.2.x master.
Dear Frantisek Erben, 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
Dear Frantisek Erben, 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
In current master, I can no longer reproduce this