FS#75476 - [pulseview] Freeze and high CPU load on startup

Attached to Project: Community Packages
Opened by Hauke Redemann (svierne) - Monday, 01 August 2022, 06:14 GMT
Last edited by Toolybird (Toolybird) - Saturday, 20 May 2023, 03:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Filipe Laíns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Pulseview freezes on startup and immediately causes high CPU load. The GUI does not initialize properly, only a black window is showing up.

Package versions:

pulseview 0.4.2-7
libsigrok 0.5.2-10
boost-libs 1.79.0-1

Steps to reproduce:

Install and run pulseview.

Workaround:

Downgrade to pulseview 0.4.2-7 and boost-libs 1.78.0-3.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 20 May 2023, 03:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  We're now on boost-libs 1.81.0-6, so assuming this is fixed.
Comment by Hauke Redemann (svierne) - Monday, 01 August 2022, 06:19 GMT
Of course, the correct versions in the workaround are pulseview 0.4.2-6 and boost-libs 1.78.0-3. Made a little typo there. :-)
Comment by Hauke Redemann (svierne) - Tuesday, 02 August 2022, 21:11 GMT
Looking at the AUR package pulseview-git [^1], the user "thierer" already found out what causes this issue and proposed a better workaround. See [^2] for the upstream bug.

In summary, the bug is locale-dependent and you can use `env LC_ALL=c pulseview` as a workaround to get pulseview running.

[^1] https://aur.archlinux.org/packages/pulseview-git
[^2] https://github.com/boostorg/multiprecision/issues/464

Loading...