[SRU] jackdbus produces high cpu load

Bug #1884101 reported by Thomas Schweikle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jackd2 (Ubuntu)
Fix Released
High
Unassigned
Focal
Won't Fix
Undecided
Unassigned
Groovy
Fix Released
High
Unassigned

Bug Description

[Impact]

 * Users have reported issues with high CPU load when running jackd and
   jackdbus, causing system slowdowns

 * This newer version was backported into the Ubuntu Studio Backports PPA
   and has shown to have success in fixing this issue.

[Test Case]

 * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

 * Killing jackd and jackdbus reduces CPU down to nominal levels

 * Version in Ubuntu Studio Backports PPA does not have this issue, same version exists in Ubuntu Groovy Gorilla.

[Regression Potential]

 * Since jackd is used by multiple professional audio applications and therefore there could be potential negative impact on those applicaitons.

 * Although that regression potential exists, multiple users have reported great success when using the newer version.

[Other Info]

 * Although not a "bug" per se, upstream developer lamented the fact that the version in 20.04 is so far behind.

 * Most audio applications and plugins in Ubuntu 20.04 have been developed with this version of Jackd in mind.

----
Original bug report:

if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sct-muc 1800 F.... pulseaudio
 /dev/snd/pcmC0D0c: sct-muc 1800 F...m pulseaudio
 /dev/snd/pcmC0D0p: sct-muc 1800 F...m pulseaudio
 /dev/snd/timer: sct-muc 1800 f.... pulseaudio
CasperMD5CheckResult: skip
Date: Thu Jun 18 18:08:25 2020
InstallationDate: Installed on 2019-09-09 (282 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Revision history for this message
Thomas Schweikle (tps) wrote :
affects: pulseaudio (Ubuntu) → jackd2 (Ubuntu)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Please install the version of jackd2 in the Ubuntu Studio Backports PPA found at https://launchpad.net/~ubuntustudio-ppa/+archive/ubuntu/backports/+packages to see if that fixes the problem. If it does, then I might be able to set-up a Stable Release Update (SRU) to get it into 20.04.

Setting as "Incomplete" for now simply to ensure a response happens in the next 60 days or this bug expires since this is critical to troubleshooting this problem.

Changed in jackd2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Schweikle (tps) wrote :

Did that already, got rid of the problem.

Changed in jackd2 (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → High
description: updated
Changed in jackd2 (Ubuntu Focal):
importance: Undecided → High
status: New → In Progress
Changed in jackd2 (Ubuntu Groovy):
status: Triaged → Fix Released
Changed in jackd2 (Ubuntu Focal):
assignee: nobody → Erich Eickmeyer (eeickmeyer)
Changed in jackd2 (Ubuntu Focal):
assignee: Erich Eickmeyer (eeickmeyer) → nobody
summary: - jackdbus produces high cpu load
+ [SRU] jackdbus produces high cpu load
Revision history for this message
Sebastien Bacher (seb128) wrote :

Erich, you unassigned yourself, do you plan to work on that fix for focal?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Oh, I see it's in the review queue so I'm going to set as fix commited and reassign

Changed in jackd2 (Ubuntu Focal):
assignee: nobody → Erich Eickmeyer (eeickmeyer)
status: In Progress → Fix Committed
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Sebastien, yeah, it's uploaded. Except proper SRU procedure is that, once I have it done, I unassign myself and let the SRU team set it as "Fix Commited", afaik. Hence, I unassigned myself and didn't change the status.

Revision history for this message
Brian Murray (brian-murray) wrote :

Assignment isn't really an important part of the SRU process from the SRU team's perspective. If there is some documentation that indicates it is please let me know.

Revision history for this message
Brian Murray (brian-murray) wrote : Proposed package upload rejected

An upload of jackd2 to focal-proposed has been rejected from the upload queue for the following reason: "This is a version bump with a wide variety of changes (according to Changelog.rst) that are not justified for SRU'ing.".

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Unfortunately, that means this bug won't be fixed in this version of Ubuntu.

Changed in jackd2 (Ubuntu Focal):
importance: High → Undecided
status: Fix Committed → Won't Fix
assignee: Erich Eickmeyer (eeickmeyer) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.