I had problems with inserting new text in a table cell. I hope you can reproduce the problem with the following procedure: Make a table. Fill in a cell with a value of a few tens of characters. Make the cell's column very narrow, say half an inch wide. The strings and words of the value will break across lines. Look at the places where words break. A word will break, of course, when there's not sufficient room for the next character. There might be a little bit of space, but not enough. Try to find a place where this little bit of space is as narrow as possible. Click at that narrow space. The caret might appear, as it should. Then try to key in a character. Now Libreoffice might hang. Or the caret might not show, Libreoffice having hanged already. If Libreoffice doesn't hang, adjust the cell width to find an even narrower space at a word break, and try again. All of Libreoffice hangs - not just Writer and the current document. Other applications might also be affected. When it hangs I can see in my System Monitor one processor running at 100%. I have tried it on one computer only, with Version: 4.2.7.2 Build ID: 420m0(Build:2) Linux Mint 17 Qiana Ubuntu 14.04.2 LTS
I was able to reproduce this in LO 4.4.3.0.0, On Windows 7 64bit LO Build ID: c9d2a2b7dfb33ea55477f3991915106ff8cae998 I set status to new and importance to high/critical, since it's a crash involving a commonly used feature.
Created attachment 114464 [details] Linux reproducer I can reproduce the issue on Linux using the attached file, from the start of the 43all bibisect repository to current master I don't have 3.3 on Linux but there's a fair chance this may be inherited from OOo
Created attachment 114465 [details] 4.4.2.1 backtraces from breaking into the hang
Procured LO 3.3.0 for Linux, reproduced -> Version: Inherited from OOo
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.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-20170522
One of those happy hours when retest on lengthy message QA Administrators yields closing a bug. Looks OK at least in 5.2.7.2.