100% CPU load when closing QJackCtl
JACK Audio Connection Kit Qt GUI Interface
Brought to you by:
rncbc
Menu
▾
▴
#33 100% CPU load when closing QJackCtl
After clicking 'Quit' in the GUI of QJackCtl 0.4.3 (Xubuntu 16.04 LTS, 32 bit) the CPU load raises to 100%. The process qjackctl is still running - it is necessary to kill it or to start qjackctl again to lower the CPU load to normal level.
The behaviour is the same if 'Enable System Tray Icon' is selected or not.
'Stop JACK audio server on application exit' is not selected.
and what does when 'Stop JACK audio server on application exit' is on?
whether this option is selected or not seems to imply you're using the jack d-bus interface and not the regular and better long supported jackd command.
unfortunately, the jack d-bus interface support on qjackctl is dead code. so to speak. i have no plans to touch it again in the near future. one single reason is: i don't develop on jack2 nor jackdbus anymore for years now. so sorry.
byee
When 'Stop JACK audio server on application exit' is enable, the CPU load does not increase on quitting. However, that is not the behaviour I would like to have (not wanting to have qjackctl runnung all the time is related to the fact that the systray icon in XFCE still does not fully work - I would be glad if I could help in debugging this).
And yes, I do use jackdbus.
Cheers, Oliver.
In case others come here for the systray issue mentioned in the previous post: by removing xfce4-indicator-plugin from the panel, the QjackCtl icon now works correctly. I could also replace all the functionality of the indicator with individual plugins.
As for the main issue of this ticket: it would still be good if 'full CPU load' can be fixed when quitting. For me, jackdbus allows happy coexistance with pulse, which is a great benefit, so I would not want to trade it in for the non-d bus variant.
There is no change in behaviour with respect to this bug in qjackctl 0.4.4.
However, I noticed that using the 'Quit' entry on the system tray icon context menu does end qjackctl correctly (no qjackctl process left, no 100% CPU load). The issue seems to be particular to the 'Quit' button on the main application window.