Bug 39583

Summary: Writer 3.3.3 and 3.4.1 causes system to become unresponsive when a modest amount of comments are used in a document
Product: LibreOffice Reporter: Matt Kelley <hundino-bugs>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: jeffdchang, yfjiang
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: A document in which the bug appears.

Description Matt Kelley 2011-07-27 00:46:44 UTC
Description:

When using Writer (3.3.3 and 3.4.1 both seem to have the issue), it appears that having a few comments can cause Fedora 15 (I'm not sure about other Linux distros) to become unresponsive.  Upon doing some sort of editing, Writer will, sometimes, stop responding, and cause the Gnome 3 system as well as the keyboard to become unresponsive.  I can still use the mouse, but the buttons don't work.  The normal button combinations to get out don't work, i.e., "ctrl + alt + backspace," "ctrl + alt + delete," and "ctrl + alt + F2."  A hard reboot is the only thing that I can use to reboot.

I have not encountered this problem on Windows using the same files that caused the issue under Fedora Linux, so I believe the issue to be isolated to Linux.

Steps to reproduce:

1.  Begin commenting on a document.
2.  Once a decent amount have been used (I found that 10 was the smallest number at which the problem occurred), keep editing the document as normal, and it will likely freeze.  There doesn't seem to be much of a pattern as to which operation it is specifically, but just sitting there doesn't seem to cause it, nor does menu navigation.

Thank you for your time!  :-)
Comment 1 Jeffrey 2011-07-28 06:52:50 UTC
Failed to reproduce on LibreOffice 3.4 340ml(Build:103) for OpenSuse Linux. Clearly it is difficult to make this statement seeing that there is no precise number or state that triggers the crash, but currently I have posted 20+ comments on one page's worth of text, and after toying around for several minutes, nothing worse than a slowdown in performance. It would be great if you could at least restore the crashed document with the comments and share it with everyone so we all have a common proven buggy document to experiment with. Also, if you could attach backtrace to the crash it would be great. Thanks!

http://wiki.documentfoundation.org/BugReport
Comment 2 Matt Kelley 2011-07-29 23:01:00 UTC
Created attachment 49737 [details]
A document in which the bug appears.

This is a scrambled file in which the bug appears (I've made sure it did after scrambling).
Comment 3 Matt Kelley 2011-07-29 23:03:11 UTC
I've scrambled the document (minus the comments since I was lazy), and have checked to make sure that the bug still appeared in the file, and it did.

I was having a little bit of trouble getting the bug to reappear (though I had encountered it several times before making the bug report) at first, but I got it to happen twice more.  I had to let the file sit open for a little while and do something other than use Writer.  The first time I used Firefox for about forty minutes, and it froze within a few (around five, I believe) minutes of random editing (deleting, adding "a"s and spaces, adding comments, and clicking and dragging selections).

The second time, I just let the computer sit for forty-five minutes before I went back to edit, and it didn't reproduce at first.  So, I opened Firefox and browsed for about five to ten minutes, then went back and it froze again after, again, about five minutes.

I'm having trouble providing you with a backtrace though (possibly because I just don't know the commands...), since the whole system locks becomes unresponsive.  As such, though I could move the mouse as before, I couldn't close the program and tell gdb to perform a backtrace.  I do still have the gdb.log file, so if something can be done with that, let me know.

Anyway, I've attached one of the files in which the bug appears.

Thank you again for your time!  :-)
Comment 4 Matt Kelley 2011-07-29 23:05:54 UTC
Oh!  I forgot to mention that I made sure to close Firefox both times to make sure the freeze wasn't a result of it and not LibreOffice.
Comment 5 Björn Michaelsen 2011-12-23 12:28:26 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 Matt Kelley 2012-01-09 17:56:05 UTC
I'd forgotten about this bug for a while, but I haven't had it pop up any more, so I believe that it's been fixed in one of the updates that LibreOffice has gone through since the filing of the report. I'm not entirely sure how to mark it, so I hope my choice is good.