High cpu usage and system unresponsive

[enorrmann]

Please fill in the following items if you don't know the root cause.

Ubuntu 23.04

GNOME 44.rc

X11 AND Wayland affected

ardout 7.3 provided by ubuntu 23.04 IBus version IBus 1.5.28-2

Issue description: high cpu usage and system unresponsive

Steps to reproduce:

1. install ardour 7.3
2. open ardour, go to CUE view
3. ibus cpu usage goes to 100% or more

the issue is not present with the binary provided by ardour.org, only with the package from ubuntu and compiling from ardour source code on ubuntu 23.04

Can you reproduce your problem when you restart ibus-daemon? (yes / no): yes

Do you see any errors when you run ibus-daemon with the verbose option?: no

Can you reproduce your problem with a new user account instead of the current your account? (yes / no): yes

[gunnarhj]

Related bug reports:

• https://launchpad.net/bugs/2012146
• https://bugs.debian.org/1033293

[fujiwarat]

Do you have a link of ardour upstream? I don't know about it.

[gunnarhj]

https://github.com/Ardour/ardour

The official one is here: https://git.ardour.org/ardour/ardour

[enorrmann]

also reported to ardour but since the bug is not present on their binaries they can't check this out https://tracker.ardour.org/view.php?id=9285

[lminiero]

@enorrmann is it still an issue for you? For a while it's been a problem for me too, and still is, and not on Ubuntu but on Fedora. I wonder if the ibus/pipewire combination is what may be causing this, e.g., in presence of many connections in Ardour?

[enorrmann]

@enorrmann is it still an issue for you? For a while it's been a problem for me too, and still is, and not on Ubuntu but on Fedora. I wonder if the ibus/pipewire combination is what may be causing this, e.g., in presence of many connections in Ardour?

I've been using the official Ardour binaries (bought them from ardour) in which this issue is not present. Also I switched to Debian 12. I will try building it from source again and report back

[enorrmann]

@enorrmann is it still an issue for you? For a while it's been a problem for me too, and still is, and not on Ubuntu but on Fedora. I wonder if the ibus/pipewire combination is what may be causing this, e.g., in presence of many connections in Ardour?

I'm sorry to inform you that with my current system configuration this is not an issue anymore debian 12 sid ibus 1.5.29~beta1-3 Ardour7.5.294 (built using 7.5-294-g92fbee6312 and GCC version 13.2.0)

is working fine

[gunnarhj]

@enorrmann wrote:

I'm sorry to inform you that with my current system configuration this is not an issue anymore debian 12 sid ibus 1.5.29~beta1-3 Ardour7.5.294 (built using 7.5-294-g92fbee6312 and GCC version 13.2.0)

is working fine

Since you are on sid, what if you use ardour 1:7.5.0+ds-2 from unstable?

[lminiero]

ibus 1.5.29~beta1-3

I guess this is the main difference, since Fedora 38 is still stuck to 1.5.28. I've found a .src.rpm of ibus 1.5.29~beta1-3 for Fedora 39, so I'll try building that on my system to see if it fixes things for me too.

[enorrmann]

ibus 1.5.29~beta1-3

I guess this is the main difference, since Fedora 38 is still stuck to 1.5.28. I've found a .src.rpm of ibus 1.5.29~beta1-3 for Fedora 39, so I'll try building that on my system to see if it fixes things for me too.

if you can confirm that is the case, will close this

[lminiero]

Unfortunately I couldn't yet: I only found src rpms for beta1-1 and beta1-2, and they both seem to still present the problem. I'll try to hunt for a beta1-3 in the next few days.

[Floby]

I can confirm that I have the same issue (ubuntu 23.04 + Ardour7.3.0~ds0 + IBus 1.5.28). The issue is present whether using wayland or X11, and also whether using PipeWire or Jack directly (although it seems to arise less frequently when running Jack).

Haven't tried using the binaries from ardour.org, but will use as a workaround for now.

[gunnarhj]

@Floby: That seems to be yet another indication that this is some kind of ardour packaging issue in Debian.

[lminiero]

I'm on Fedora, not Debian, and I'm getting the same behaviour.

[gunnarhj]

@lminiero: Ack.

[fujiwarat]

I cannot reproduce your issue.