[Konsole-devel] [Bug 99746] 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         




------- Additional Comments From bugs.kde.org matthew mulrooney ca  2005-02-19 20:20 -------
Oops, those attachments overwrote my response to Kurt.  Here it is again:

Hey Kurt - my replication instructions were not as clear as they should have been.  My intent was to demonstrate the Konsole locking up for a few seconds, and pegging the CPU at 100% during that time.

Konsole always *does* come back with the "not found" message, but in the mean time it leaves the user wondering what has happened.

To appreciate this, one would have to have a history of many million lines, and then do a search for a non-existent string.  

In my case, I have had:

  - history set to "unlimited"
  - a *huge* history
  - and a search string containing a typo (therefore an unfindable search string)

Yesterday I had Konsole go away for 15 minutes on a P4 2.5GHz, 1GB RAM.  That was somewhat uncomfortable as I did it on my organizations build server :/.  Oops :).