Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI(+CLI) Entire UI freezes during long opperation (e.g. delete). #1192

Open
fromSmolsoft opened this issue Jan 24, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@fromSmolsoft
Copy link

fromSmolsoft commented Jan 24, 2024

Bug Description
Entire UI layer freezes when intensive operations like delete thousands of dupes is initiated despite CPU / RAM / drive are not fully used.
On Windows it goes into full foggy screen mode on top of mentioned and covers even panel with launcher icons.

Steps to reproduce:

  1. scan data worth of 10-100 thousand files and 20 to 100 GB
  2. pick few thousands of dupes and press delete or move
  3. watch entire app (UI) to freeze for undefined period while CPU / RAM / Drive usage is bellow 30 % OS usage included.

IMHO it looks as if UI and background processes run on same thread, so the UI hangs.
Interestingly when search is initiated, little alert dialog with progress bars doesn't freeze,

System
Basic specs of machines:

  • CPU: intel 2, i3, i7;
  • RAMs: 3GB, 6GB, 16GB;
  • drives: HDD, SSD;
  • OS: Lin mint 21.2, Lin mint 21.2, Win11

Czkawka behaves exactly the same on each device.

  • Czkawka version:
    • Czkawka GUI +CLI 6.1.0, Windows, was compiled with release mode
    • Czkawka GUI (flatpack) on Linux
@fromSmolsoft fromSmolsoft added the bug Something isn't working label Jan 24, 2024
@fromSmolsoft fromSmolsoft changed the title GUI(+CLI) Entire UI layer freezes when long opperation (delete) takes place. GUI(+CLI) Entire UI freezes during long opperation (e.g. delete). Jan 24, 2024
@AndroYD84
Copy link

Having the same problem. The GUI has been stuck like this for 3 days while doing a mass symlink operation. It takes about 3 days to complete a scan (with cached hashes), so without a import feature as suggested here #1295 there's no way to recover from failure and we lose all progress, it's like walking on egg shells this is incredibly frustrating.
czkawkafreeze01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants