Description: LibreOffice gets unresponsive (does not respond) under certain circumstances Steps to Reproduce: 1. Open the attachment 145863 [details] 2. After document show up. Immediately press a key (say A or D). Hold it until it stops responding. (between 5-8 rows... 3. The document will lock down & LibreOffice gets unresponsive Actual Results: LibreOffice gets unresponsive Expected Results: LibreOffice should be responsive at some point Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha1+ Build ID: 2e184378da6058af14acf208d6469fadf44d04ed CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-30_03:29:39 Locale: nl-NL (nl_NL); Calc: CL Lots of time spend in: SwContact::ObjAnchoredAtFly
Thank you for reporting the bug.I can confirm that the bug is present in Version: 6.0.6.2 Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group
I can't reproduce it in Version 4.1.0.0.alpha0+ (Build ID: 2bbb4b9c5bf9c61c5b0b7fdfcce5b97e04a63a8)
Actually it hangs in Version 4.1.0.0.alpha0+ (Build ID: 2bbb4b9c5bf9c61c5b0b7fdfcce5b97e04a63a8) as well
However, it doesn't in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 kind of an old regression...
I got a different result: no hang in 4.1-4.4. Bibisected with 50max to the Timer/Idle range, which seems fitting: https://gerrit.libreoffice.org/plugins/gitiles/core/+log/e6e8a060ecc6e4fd51cfe88e00d841d546ed5915..01f406bc28f53acc5a2734af637aa8074a5d1813 It was not a straight up hang, it just got very slow. I was able to quit normally each time.
(In reply to Buovjaga from comment #5) > I got a different result: no hang in 4.1-4.4. Bibisected with 50max to the > Timer/Idle range, which seems fitting: > https://gerrit.libreoffice.org/plugins/gitiles/core/+log/ > e6e8a060ecc6e4fd51cfe88e00d841d546ed5915.. > 01f406bc28f53acc5a2734af637aa8074a5d1813 > > It was not a straight up hang, it just got very slow. I was able to quit > normally each time. Thanks for bibisecting. These types of bibisects are the most frustrating ones to do.
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://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 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