The Program will on hold when screen saver on.

[ffchung]

Bug Description
The Program will on hold (freeze or stop at before Screen Saver start) until I active the screen again (Back from Screen Saver). The progress will resume.
Steps to reproduce:

When the program start scan the folder. And wait it Screen Saver on . And wait some time and going back. You can see in the Activity Monitor the network active down to zero at screen saver on and back to normal when screen saver off.

Terminal output (optional):

<!--
Add terminal output only if needed - if there are some errors or warnings or you have performance/freeze issues.  
Very helpful in this situation will be logs from czkawka run with RUST_LOG environment variable set e.g. 
`RUST_LOG=debug ./czkawka` or `flatpak run --env=RUST_LOG=debug com.github.qarmin.czkawka` if you use flatpak, which will print more detailed info about executed function.
-->

<details>
<summary>Debug log</summary>

# UNCOMMENT DETAILS AND PUT LOGS HERE

</details>

System

OSX 15.6.1
Mac mini M2.

Czkawka gtk version: 10.0.0(76f4e03 U 2026-02-05), release mode, rust 1.93.0 (2026-01-19), os Mac OS 15.6.1 (aarch64 64-bit), 10 cpu/threads, features(3): [heif, libavif, libraw], app cpu version: Baseline, os cpu version: Baseline

• Czkawka/Krokiet version:
• OS version:
• Installation method:

[qarmin]

This does not look like an application issue to me, but rather expected system behavior where the OS aggressively suspends applications when the screen saver is active.

I could perhaps accept that GTK, upon receiving a system event, might pause and stop rendering, but the core has absolutely no handling of system events. It simply runs until it is stopped or finishes its work.

I do not own a Mac, but there are references online to mechanisms such as App Nap, which could theoretically cause this kind of behavior.

[ffchung]

It look like the queue handle by UI Thread. When I put the app run at background (Not show on desktop or fully cover by other window). It will process for a while and stopped (look like finish the current hash process). After I pull it back and it will work again. It mean when it don't have UI work to do and it will not process job in queue.