Overview: When I'm closing firefox it's not exiting and then kwin helper popups with suggestion to kill the window. After aproving window killing kwin_killer_helper hangs with 100% CPU usage. But if I'm kill firefox simply executing "kill <firefox pid>" it exits normally and kwin_killer_helper also exits. Steps to Reproduce: 1) Start firefox 2) Try to close it Actual Results: 1) Firefox window still exists 2) kwin_killer_helper hangs with 100% CPU usage Expected Results: 1) Application should be closed correctly
Created attachment 114309 [details] kwin_killer_helper flamegraph
Created attachment 114310 [details] kwin_killer_helper core file
Created attachment 114311 [details] .asoundrc file using which we have a problem I'm using custom .asoundrc which uses jackd. If I switch back to default configuration there is no problem with closing window. jackd is launched this way: jackd -T -d alsa
Can you get a back trace in gdb of kwin helper whilst its using 100% cpu
Oh you have. sorry.
So the bug is in frameworks integration adding notification with sound support to KMessageBox. There's a port on frameworks that should fix that soon.
Btw, I've meet the same problem with org_kde_powerdevile (sorry for posting it here) but here the backtrace of thread which use 100% CPU: Thread 7 (Thread 0x7f022c143700 (LWP 14031)): #0 0x00007f0251f01483 in __GI___poll (fds=0x7f022c142c80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f022f55d10f in ?? () from /usr/lib64/libasound.so.2 #2 0x00007f022f59ea14 in ?? () from /usr/lib64/libasound.so.2 #3 0x00007f022f7f2d05 in ?? () from /usr/lib64/vlc/plugins/audio_output/libalsa_plugin.so #4 0x00007f02387831c2 in ?? () from /usr/lib64/libvlccore.so.9 #5 0x00007f0238765f9c in ?? () from /usr/lib64/libvlccore.so.9 #6 0x00007f024f16f96a in start_thread (arg=0x7f022c143700) at pthread_create.c:463 #7 0x00007f0251f0d05f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Created attachment 114321 [details] powerdevil backtrace
yeah, you'll hit it with everything with a notification in any kde app.
@David did that port ever happen? Is this still relevant?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!