Bug 157965

Summary: konsole freezes when shell is busy
Product: [Applications] konsole Reporter: Seb <bastisemail>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Seb 2008-02-17 12:32:50 UTC 
Version:            (using KDE 4.0.1)
Installed from:    SuSE RPMs
OS:                Linux

I hope I did analyze this problem correctly, probably you may correct me if I am wrong.

When hitting the tab key in bash, one may display all possible choices for filename completion. The very first time doing this operation, it takes some time. During this time, the whole konsole app is not responding. I have the impression, this did not happen in KDE3 (or maybe it was just faster :) )
Comment 1 Robert Knight 2008-02-17 13:20:48 UTC 
This might be related to #bug 156191 

> During this time, the whole konsole app is not responding.

Odd.  The only possibility I can think of is Konsole freezing while KNotify is set up to make a bell noise.  In that case the same effect will happen if you press the Backspace key in an empty prompt.  Is this the case?
Comment 2 Seb 2008-02-17 17:11:29 UTC 
Yeah, it is the same problem. But I already solved it by myself (it probably is no bug of konsole at all). Xorg constantly used 100% cpu time due to some new plasmoids I downloaded from openSUSE's building service. Therefore, it may have taken a while. Due to the same reason the whole desktop was unresponsive ta the same time. I close this bug report again. But it is, off course, interesting that particularly the konsole app reacts sensitive to cpu loading. This should definitely be optimized, since I kill jobs mostly using 'top' in a terminal.
Comment 3 Robert Knight 2008-02-17 19:22:14 UTC 
> interesting that particularly the konsole app reacts sensitive to cpu loading

I don't think it is as simple as that.  CPU intensive tasks such as program compilation are run in the terminal all the time without causing any problems.  Linux is pretty good at keeping the system responsive under processor load.

If X.org or something else is using vast amounts of memory as well as CPU time then the system may end up swapping everything else out the hard disk which will cause the whole system to slow down.  If you run out of memory and there is nothing in place to kill off the offending processes then the whole system will grind to a halt.

Without really understanding the conditions under which the problem occurs I cannot make any changes to Konsole.