Bug 401981 - "Use all cores" opens n threads but they running all at one core
Summary: "Use all cores" opens n threads but they running all at one core
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-Core (show other bugs)
Version: 5.9.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-10 21:54 UTC by lutz.labusch
Modified: 2022-01-02 22:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lutz.labusch 2018-12-10 21:54:24 UTC
Hi,

if i switch on the option "use all cores" in the behavior tab, the programm opens 32 threads, which is the number of the available threads, but all of them running at one core (visible at ksysguard and htop).

System is Opensuse Leap 15, fresh install, only amdgpu-pro for the opencl stack is installed. Digikam 5.9, KDE-Plasma 5.12.6, KDE-Framework 5.45.0, Qt 5.9.4.

Thanks and regards!

This behavior is reproducible at my side. 
But was not observed at Kubuntu 18.04 with Digikam 5.6
Comment 1 Maik Qualmann 2018-12-11 07:08:46 UTC
Gilles, can you reproduce it with digiKam-6.0.0-beta3? here with me all cores are used.

Maik
Comment 2 lutz.labusch 2018-12-12 21:19:19 UTC
Hi,

I tested bare installations of OpenSuse Leap 15 and Tumbleweed in VirtualBox.

Leap 15 behaves like described
Tumbleweed behaves as expected, all cores running.
Kubuntu 18.04 behaves like expected.
Comment 3 Maik Qualmann 2018-12-12 21:26:28 UTC
Strange..., Can you test the current AppImage under OpenSuse Leap 15?

https://files.kde.org/digikam/

Maik
Comment 4 lutz.labusch 2018-12-12 21:42:16 UTC
I tried both

6.0.0-beta3.appimage and 5.9.0-01appimage.

Both quits with "memory access error"

Lutz
Comment 5 caulier.gilles 2018-12-12 22:13:08 UTC
No i cannot reproduce this dysfunction, with AppImage or with system compiled version.

Gilles
Comment 6 lutz.labusch 2018-12-16 21:32:41 UTC
https://bugzilla.opensuse.org/show_bug.cgi?id=1119469

The solution from this error solves the problem.