GNOME Bugzilla – Bug 366060
-Melkje bug- Gedit uses 100% CPU with one long lined documents when selected as active program.
Last modified: 2006-10-29 09:55:24 UTC
Please describe the problem: When Gedit has a long one lined document opened and the window is active (selected in metacity) the CPU rises to 100%. When the window is deselected the CPU drops down to a more logic 99% idle. Tested other big documents (like http://www.gutenberg.org/files/18362/18362.txt which is many times larger) and other recursive text documents with more lines but none show up this problem. So it seems like the long line is the problem. Steps to reproduce: 1. Open the attachment (or type a word, select it and copy paste it a few hundred times) 2. Watch the CPU 3. Deselect the window and see the CPU drop 4. Select the window again and see the CPU going back to 100% again. Actual results: Full CPU usage, slow system, Gedit not responding like it should (very slow or not at all) Expected results: An idle CPU when doing nothing (no scrolling, editing or anything else) Does this happen every time? Yes Other information: Tested on 2 pc's (both Ubuntu edgy with gnome 2.16.1). This bug is found because Joep (my colleague) was messing around with gedit and the infamous word "Melkje" and his two favorite key combinations CTRL+C and CTRL+V. Keep the good software coming!
Created attachment 75546 [details] Compressed large 1 line document that causes this bug Extract the file before opening in Gedit.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 114337 ***