[Konsole-devel] [Bug 99746] New: Lock-up when when performing "Find in History" on konsole that has a long history

[Matthew Mulrooney]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=99746         
           Summary: Lock-up when when performing "Find in History" on
                    konsole that has a long history
           Product: konsole
           Version: 1.4
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: konsole-devel kde org
        ReportedBy: bugs.kde.org matthew mulrooney ca


Version:           1.4 (using KDE 3.3.2, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.9-gentoo-r9

Problem description
===================
Performing a "Find in History", "Find Previous", or "Find Next" within a Konsole instance that is configured with:

  Setting > History... > Number of lines = Unlimited

can lock that Konsole instance, and peg your CPU at 100% usage for very long period of time.  [This requires that your search string doesn't exist in Konsole's history, and that you have a *very* large history.]

If possible, can a "Cancel search", "Cancel find", or "Cancel operation" button be added?

To replicate the problem
========================
[This was tested on a PIII 866 with 512MB of RAM.]

Launch a new Konsole Set your History to 500,000 lines.

$ su - root
$ cd /var/log
$ while true; do for fn in `find . | grep \.log$`; do \
echo ${fn}; cat ${fn}; done; done

Scroll up to the top of your history and hang out there until text begins to scroll by.  Hit Ctrl-C.  Your Konsole history is now full.

Now perform a:

  Edit > Find in History... 
    Find = "slkdfjlsdjflskdfjl"
    Find backwards = checked

Then hit "Find".