https://issues.apache.org/ooo/show_bug.cgi?id=121474
Nicholas Zynko <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from Nicholas Zynko <[email protected]> --- I was able to reproduce this bug in OO Writer v3.4.1 on a Windows 7 x64 machine. I did this using the sample document provided by the original poster. How to Replicate: 1. Open or create XML form document with fields. 2. Type text into field at a normal pace so that the “undo” feature only deletes a character or a single word at a time. (If a user copies and pastes text in massive amounts it will not have a greater effect.) 3. Continue until the memory in use by the soffice.bin process is between 79,000 kilobytes and 85,000K kilobytes. At this point, Write should slow down or crash. Following the method above I was able to crash the program twice. I gave careful attention to the change in memory while trying to crash the program. In both instances, I noticed that it didn’t matter if I typed in single characters at a time or pasted massive amounts of text; that both methods increased memory by the same amount. I accomplished both crashes by typing in two different fields on two separate pages. I tried deleting the text I entered in both occurrences, but the memory did not reduce. The rate of increase in memory was about 100 kilobytes for each handful of characters I typed. When I first opened the XML form, the memory was about 39,000 kilobytes. The first crash occurred at approximately 79,500 kilobytes, and the second crash occurred at approximately 81,000 kilobytes. On the second crash the characters I entered into the field became invisible, even as I continued to type. I could not get them to reappear again. Writer also came to a crawl in terms of response time. I continued to type after this for a few seconds and the program finally crashed. My Thoughts: The nature of this seems that it may be a stack overflow for the undo/redo feature. It did not matter if I slowly typed a single character at a time, or repeatedly pasted in a page’s worth of text at a time for the result was the same. Typically every time a change is made in a text editor, all the data associated with that change is thrown onto a stack so that a user may undo it. Overflowing this stack may cause the program to crash. This issue also seems to be pretty important due to the fact that this bug can affect many users and it is relatively easy to trigger. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
