Bug 343347 - Konsole occupy all CPU when closed
Summary: Konsole occupy all CPU when closed
Status: RESOLVED DUPLICATE of bug 343803
Alias: None
Product: konsole
Classification: Applications
Component: single-process (show other bugs)
Version: 3.0.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-26 20:08 UTC by Xwang
Modified: 2016-01-22 15:09 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xwang 2015-01-26 20:08:16 UTC
When I close Konsole with the x window button, it start to use all the CPU it is running on (on my 2 core pc it uses 50% of overal CPU time). So I have to kill it.

Reproducible: Always

Steps to Reproduce:
1.Open Konsole
2.Close it with the X button
3.

Actual Results:  
It starts using all the CPU

Expected Results:  
It closes.
Comment 1 Christoph Feck 2015-01-26 23:36:27 UTC
Could be related to Input Methods. Are you using ibus or fcitx?
Comment 2 Damien Gombault 2015-01-27 15:27:42 UTC
Hi.

I have recently upgraded my Arch Linux system.
Konsole is now in version 3.0.1 (KDE Apps 14.12).

I also noticed this problem since this upgrade.
It happens often when I close Konsole with the X button or with Menu File → Close the window.
It is not properly closed and uses 100% CPU, I have to kill it.

Sometimes, I also get some strange memory error when I close it :

 *** Error in `konsole': double free or corruption (fasttop): 0x00007f55d80008c0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x732ae)[0x7f55f3b142ae]
/usr/lib/libc.so.6(+0x7872e)[0x7f55f3b1972e]
/usr/lib/libc.so.6(+0x78eeb)[0x7f55f3b19eeb]
/usr/lib/libQt5Core.so.5(_ZN14QObjectPrivate10ConnectionD1Ev+0x26)[0x7f55f067e4a6]
/usr/lib/libQt5Core.so.5(_ZN7QObjectD1Ev+0x2e9)[0x7f55f0688ec9]
/usr/lib/libQt5Core.so.5(_ZN7QThreadD1Ev+0x8d)[0x7f55f046086d]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x5b771)[0x7f55dfd58771]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x30391)[0x7f55dfd2d391]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x309a9)[0x7f55dfd2d9a9]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x34fbe)[0x7f55dfd31fbe]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x35099)[0x7f55dfd32099]
/usr/lib/libQt5Gui.so.5(_ZN22QGuiApplicationPrivateD1Ev+0x160)[0x7f55f0972e10]
/usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivateD0Ev+0x9)[0x7f55f0f29b59]
/usr/lib/libQt5Core.so.5(_ZN7QObjectD1Ev+0x48b)[0x7f55f068906b]
/usr/lib/libQt5Widgets.so.5(_ZN12QApplicationD1Ev+0x343)[0x7f55f0f2b693]
/usr/lib/libkdeinit5_konsole.so(kdemain+0x714)[0x7f55f3e66544]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7f55f3ac1040]
konsole[0x40076e]

Or

*** Error in `konsole': corrupted double-linked list: 0x00007f35f40008d0 ***

I do not use ibus or fcitx.
Comment 3 Damien Gombault 2015-01-27 15:29:35 UTC
I have also theses messages in dmesg :
[janv.27 01:11] traps: QXcbEventReader[24650] general protection ip:7fab4076f8f3 sp:7fab2a7fcc30 error:0 in libc-2.20.so[7fab406f7000+199000]
[janv.27 01:12] traps: QXcbEventReader[24774] general protection ip:7f5f3f0d18f3 sp:7f5f2915ec30 error:0 in libc-2.20.so[7f5f3f059000+199000]
[  +0,906206] traps: QXcbEventReader[24787] general protection ip:7f47360b28f3 sp:7f472013fc30 error:0 in libc-2.20.so[7f473603a000+199000]
[janv.27 01:13] traps: QXcbEventReader[25007] general protection ip:7f6f6404a8f3 sp:7f6f4e0d7c30 error:0 in libc-2.20.so[7f6f63fd2000+199000]
[janv.27 01:17] traps: QXcbEventReader[25197] general protection ip:7fe972d4b8f3 sp:7fe95cdd8c30 error:0 in libc-2.20.so[7fe972cd3000+199000]
[  +3,761496] traps: QXcbEventReader[25210] general protection ip:7fda02d6f8f3 sp:7fd9ecdfcc30 error:0 in libc-2.20.so[7fda02cf7000+199000]
[ +13,472557] traps: QXcbEventReader[25242] general protection ip:7f8dc6f678f3 sp:7f8db0ff4c30 error:0 in libc-2.20.so[7f8dc6eef000+199000]

I think this is related.
Comment 4 Xwang 2015-01-27 17:02:39 UTC
(In reply to Christoph Feck from comment #1)
> Could be related to Input Methods. Are you using ibus or fcitx?

As far I can see, I'm using nor ibus neither fcitx since those programs are available but not installed on my system.
Comment 5 Xwang 2015-01-27 23:40:03 UTC
When it happens (at least the last timne it has occured) I've found this in dmesg:
QXcbEventReader[26610]: segfault at 7f4ce40008c8 ip 00007f4c085378f3 sp 00007f4bf2657c30 error 4 in libc-2.20.so[7f4c084bf000+199000]
which seems simila to Damien Gombault ones.
Comment 6 Matteo De Carlo 2015-01-31 21:12:28 UTC
I tryed with one of my friends. We both have archlinux, but he is using kde4 and I'm using kde5. He is using bash and I'm using zsh. The issue is the same.
Every time you press the X button (or alt-f4), the window closes but if you check the resource usage the konsole process (bash/zsh are already killed) are using 100% of one core. Still the process can be terminated with signals TERM and HUP. That means that the process is not completely unresponsive.
When instead bash/zsh is closed (ctrl-d or exit command), everything works as expected. 

Konsole 3.0.1
K Frameworks 5.6.0
Comment 7 kamikaazewiesel 2015-02-20 09:32:36 UTC
Can confirm this behavior, even though it happens only most of the time. Sometimes it seems to close as expected.
This also happens after a fresh install of kde.

Konsole 3.0.1
Platform Version 4.14.5
Comment 8 Francois van der Ven 2015-02-22 11:48:47 UTC
*** This bug has been confirmed by popular vote. ***
Comment 9 Jan Buchar 2015-03-27 22:05:06 UTC
I tried debugging a hanging Konsole with gdb and got this:

(gdb) thread apply all bt

Thread 2 (Thread 0x7ff8b9157700 (LWP 3809)):
#0  0x00007ff8d75491b3 in select () from /usr/lib/libc.so.6
#1  0x00007ff8d3f61a61 in ?? () from /usr/lib/libQt5Core.so.5
#2  0x00007ff8d3de355e in ?? () from /usr/lib/libQt5Core.so.5
#3  0x00007ff8cf65f374 in start_thread () from /usr/lib/libpthread.so.0
#4  0x00007ff8d755027d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ff8d7a46800 (LWP 3807)):
#0  0x00007ff8ca640e25 in _nv014tls () from /usr/lib/libnvidia-tls.so.346.47
#1  0x00007ff8ce58a3e6 in ?? () from /usr/lib/libGL.so.1
#2  0x00007ff8ce58a727 in ?? () from /usr/lib/libGL.so.1
#3  0x00007ff8ce58a81a in ?? () from /usr/lib/libGL.so.1
#4  0x00007ff8ce564885 in ?? () from /usr/lib/libGL.so.1
#5  0x00007ff8d7a57815 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#6  0x00007ff8d749ddb2 in __run_exit_handlers () from /usr/lib/libc.so.6
#7  0x00007ff8d749de05 in exit () from /usr/lib/libc.so.6
#8  0x00007ff8d7488807 in __libc_start_main () from /usr/lib/libc.so.6
#9  0x0000000000400779 in _start ()
Comment 10 Vladimir 2015-08-29 19:34:27 UTC
I confirm this. Kubuntu 15.04, (15.04.0 KDE Frameworks 5.12.0).
Comment 11 Xwang 2015-09-02 20:32:01 UTC
It is present also in 15.08.00
Comment 12 Sandro 2015-10-21 13:42:06 UTC
I also have this bug. gdb backtrace is identical to the Jan Buchar's one.

Debian testing, konsole 15.08.1
Comment 13 Andreas Blochberger 2015-12-20 09:23:50 UTC
This is a duplicate of Bug 343803
Comment 14 Rex Dieter 2016-01-22 15:09:04 UTC

*** This bug has been marked as a duplicate of bug 343803 ***