Bug 505619

Summary: Strange behavior of cores processors
Product: [Applications] digikam Reporter: neo.49
Component: Setup-MiscAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: caulier.gilles
Priority: NOR    
Version First Reported In: 8.7.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 8.9.0
Sentry Crash Report:
Attachments: CPU Cores Display in Task Manager
Config Behavior
DebugView log

Description neo.49 2025-06-15 07:12:10 UTC
Created attachment 182280 [details]
CPU Cores Display in Task Manager

SUMMARY
After launching digikam, my processors' graph is displayed weirdly.
One of my core processor is showing less activity than the others.
And after closing digikam, the activity on this core returns to normal

STEPS TO REPRODUCE : I don't know how to.
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
DigiKam: 8.7.0
Environnement de développement de KDE: 6.12.0
Qt: Par utilisation de 6.8.3 et avec compilation avec 6.8.3
Windows 11 Version 24H2
Build ABI: x86_64-little_endian-llp64
Kernel: winnt 10.0.26100


ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2025-06-15 08:05:41 UTC
Please look In the digiKam/Setup/Mics/Behaviors configuration dialog page which processes are started at startup which can require processor to analyze database contents. These process can slow down the startup...

https://docs.digikam.org/en/setup_application/miscs_settings.html#behavior-settings
Comment 2 neo.49 2025-06-21 08:36:35 UTC
Created attachment 182476 [details]
Config Behavior
Comment 3 neo.49 2025-06-21 08:39:30 UTC
Hello,
I have configured the page quite the same as the documentation page (see attachment).
Sorry, the UI is in french because I'm French ;)

For testing I deactivated all external plugins ("Modules externes"), but no change noticed.
Comment 4 caulier.gilles 2025-06-25 06:03:24 UTC
Hi,

I'm French too, so your screen shot are fine (:-)))...

Please disable the option "Activer l'analyze de reconnaissance faciale en arrière plan", restart digiKam, and try again.

Best

Gilles Caulier
Comment 5 neo.49 2025-06-29 06:06:47 UTC
Hello Gilles,

I've tried what you say, but unfortunately, no change.
Comment 6 caulier.gilles 2025-06-29 06:59:24 UTC
ok, 

Install debugView and use it as explained here :

https://www.digikam.org/contribute/#windows-host

Restart digiKam and reproduce the CPU idle. Capture the trace and CC in this file for analysis.

Gilles Caulier
Comment 7 neo.49 2025-06-30 16:11:19 UTC
Hello Gilles,
Here is the log of the DebugView.
Comment 8 neo.49 2025-06-30 16:11:54 UTC
Created attachment 182801 [details]
DebugView log
Comment 9 caulier.gilles 2025-07-01 07:27:10 UTC
You have strange message which do not come from digiKam at all, as:

00000287	7.79265118	[22828] SetProcessDPIAwareness failed. (Acc�s refus�.)	
00000288	7.79279137	[22828] CreateWindow() for QEventDispatcherWin32 internal window failed (L�op�ration a r�ussi.)	
...
00000306	10.02274609	[10128] [2025.06.30-16.01.09:654][305]NIM_ADD returned error -2147467259 	
00000307	10.02280998	[10128] [2025.06.30-16.01.09:654][305]AddNotificationIcon failed after 10 attempts 	
00000308	16.30883789	[10128] [2025.06.30-16.01.15:939][439]NIM_ADD returned error -2147467259 	

The first one is a Windows call to setup the DPI to use with an application:
https://learn.microsoft.com/fr-fr/windows/win32/api/shellscalingapi/nf-shellscalingapi-setprocessdpiawareness

The NIM_ADD error is about to host icon in Windows status bar :
https://learn.microsoft.com/en-us/windows/win32/api/shellapi/nf-shellapi-shell_notifyiconw

No idea why these errors appears. The rest of the log is normal.

Gilles Caulier
Comment 10 caulier.gilles 2025-07-01 11:59:31 UTC

*** This bug has been marked as a duplicate of bug 506432 ***
Comment 11 caulier.gilles 2025-12-15 14:38:36 UTC
Fixed with bug 506432