Won't stop

[github-account1111]

Bug Description

I ran "Duplicate Files" on a directory on an external drive. It was taking forever with no progress indication, so I clicked Stop. It is now stuck on "Stopping scan"? I can hear the disk spinning non-stop.

It's also writing something to it:

What is happening?

Steps to reproduce:

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

• Krokiet version: 11.0.1
• OS version: Windows 10 22H2
• Installation method: GitHub

[qarmin]

Are there any errors in the logs?
I suspect the disk is quite slow (probably an HDD), where accessing ~1 million files quickly is problematic. Also, the hide_hard_links option is enabled by default, which after scanning requires checking every single file inodes and removing hard links from the results - you can try to disable this option to see if this will help

[github-account1111]

Yes it's an external HDD but a fairly fast CMR one which reaches ~200 MBps in both reads and writes.

The log:

2026-04-11 14:13:26.972 [INFO] [czkawka_core::common::logger] (1) logger.rs:58 - Logging to file "C:\Users\pj\AppData\Local\Qarmin\Czkawka\cache\krokiet.log" and terminal
2026-04-11 14:13:26.972 [INFO] [czkawka_core::common::logger] (1) logger.rs:176 - Krokiet version: 11.0.1(9e40abeae2 O 2026-02-20), release mode, rust 1.92.0 (2025-12-08), os Windows 10.0.19045 (x86_64 64-bit), 16 cpu/threads, features(0): [], app cpu version: x86-64-v1 (SSE2), os cpu version: x86-64-v4 (AVX-512)
2026-04-11 14:13:26.972 [INFO] [czkawka_core::common::config_cache_path] (1) config_cache_path.rs:186 - Config folder set to "C:\Users\pj\AppData\Roaming\Qarmin\Krokiet\config" and cache folder set to "C:\Users\pj\AppData\Local\Qarmin\Czkawka\cache"
2026-04-11 14:13:26.972 [INFO] [krokiet] (1) main.rs:227 - Krokiet features(2): [winit_femtovg, winit_software]
2026-04-11 14:13:27.005 [DEBUG] [czkawka_core::common] (1) mod.rs:96 - Number of threads set to 0 (0 - means that all available threads will be used(16))
2026-04-11 14:14:06.212 [INFO] [czkawka_core::tools::duplicate::traits] (21) traits.rs:38 - find_duplicates
2026-04-11 14:14:06.212 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:226 - check_files_size
2026-04-11 14:14:06.213 [DEBUG] [czkawka_core::common::dir_traversal] (21) dir_traversal.rs:212 - run(collecting files/dirs)
2026-04-11 14:14:07.249 [DEBUG] [czkawka_core::common::dir_traversal] (21) dir_traversal.rs:363 - Collected 969732 files
2026-04-11 14:14:07.249 [DEBUG] [czkawka_core::common::dir_traversal] (21) dir_traversal.rs:212 - run(collecting files/dirs): Done in 1.04s
2026-04-11 14:47:28.913 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:268 - check_file_size - filtered hard links in 2001.6366014s, removed 0 hardlinks (573308 -> 573308)
2026-04-11 14:47:28.914 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:310 - filter_reference_folders_by_size
2026-04-11 14:47:28.914 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:310 - filter_reference_folders_by_size: Done in 224.30µs
2026-04-11 14:47:28.919 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:279 - check_file_size - after calculating size stats/duplicates, found in 176653 groups, 573308 files with same size | referenced 0 groups, 0 files
2026-04-11 14:47:28.919 [DEBUG] [czkawka_core::tools::duplicate::core] (21) core.rs:226 - check_files_size: Done in 2002.71s
2026-04-11 14:47:28.919 [DEBUG] [czkawka_core::tools::duplicate::traits] (21) traits.rs:20 - delete_files
2026-04-11 14:47:28.919 [DEBUG] [czkawka_core::tools::duplicate::traits] (21) traits.rs:20 - delete_files: Done in 4.00µs
2026-04-11 14:47:28.919 [INFO] [czkawka_core::tools::duplicate::traits] (21) traits.rs:38 - find_duplicates: Done in 2002.71s
2026-04-11 14:48:07.832 [DEBUG] [krokiet::connect_show_preview] (1) connect_show_preview.rs:112 - Loading and converting image in slint - loading image: 30.5638ms, converting image to Slint image: 344.7µs, setting image in GUI: 1.3µs, total: 31.0454ms
2026-04-11 14:48:09.763 [DEBUG] [krokiet::connect_show_preview] (1) connect_show_preview.rs:112 - Loading and converting image in slint - loading image: 548.4µs, converting image to Slint image: 103.4µs, setting image in GUI: 1.8µs, total: 654.9µs

It did stop a few minutes after I opened this issue, but it had already been showing "Stopping scan" for ~10 minutes prior to that. Regardless, why didn't it just do it when I clicked the button? Software isn't a car. It shouldn't need a "stopping distance", let alone so much of it. What would've happened if I had closed the program instead of waiting for it to finish, seeing how it was writing something to disk?

I did just realize my "Thread number" slider was set to 0 which may or may not mean "all" (but then what would 16/16 mean?). I've moved it to 1 and will see how things go during the next run. Multithreading is a complete no-go with hard drives, both in terms of performance and longevity.