-
-
Notifications
You must be signed in to change notification settings - Fork 676
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
Hanging near the end of the similar images scan #256
Comments
Almost half million of scanned images is quite a big number, but it shouldn't infinitely hang an app. What OS and GTK version do you have? Can you run app from gdb?
this should print backtrace what actually do app(it will freeze it) |
Will do. It has been running for 30+ hours and over 12 of just sitting
there using very little cpu and spare memory.
This is on Ubuntu 20.10 on a Dell XPS 13 w/ 16gb of RAM and nothing else
really running
I’ll spin up a GDB run later today.
…On Thu, Feb 11, 2021 at 10:55 AM Rafał Mikrut ***@***.***> wrote:
Almost half million of scanned images is quite a big number, but it
shouldn't infinitely hang an app.
At the end, just before hiding progress window, Czkawka must compare
hashes, save results to cache, send them to GUI and at the end show in GUI
similar images.
I think that all steps shouldn't take more than 10 second.
What OS and GTK version do you have?
Are you sure that app have enough ram to work(similar images needs even a
few GB depends on number of processors)?
Can you run app from gdb?
gdb
file /home/rafal/.cargo/bin/czkawka_gui
run
# Now reproduce freeze
# Click CTRL + C
backtrace
this should print backtrace what actually do app(it will freeze it)
to resume app just print continue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#256 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGUOXVWGH5AYSGA7GK7X5LS6QKXXANCNFSM4XPFJZ6A>
.
|
OK - ran with gdb. Seems like what I was seeing before in the strace - lots of polling and nothing going on. I still have it sitting here in GDB - anything to look for?
|
Looks that there is a non handled crash in other thread inside Czkawka. Please run czkawka from command line with adding before variable to get detailed backtrace
You should see backtrace similar to #237 If you would find image which cause crash, it will allow to open new issue in https://github.com/image-rs/image/ just like here - image-rs/image#1420 |
Run it with ‘RUST_BACKTRACE’ in GDB? Or just adding the backtrace to a
normal startup?
…On Sat, Feb 13, 2021 at 3:35 PM Rafał Mikrut ***@***.***> wrote:
Looks that there is a non handled crash in other thread inside Czkawka.
Only place where it can crash in such way is external image library
image-rs.
Please run czkawka from command line with adding before variable to get
detailed backtrace
RUST_BACKTRACE=1 czkawka_gui
You should see backtrace similar to #237
<#237>
If you would find image which cause crash, it will allow to open new issue
in https://github.com/image-rs/image/ just like here - image-rs/image#1420
<image-rs/image#1420>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#256 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGUOXVYWEGBTXEI2SQAGDDS635B5ANCNFSM4XPFJZ6A>
.
|
Without GDB, just like you open normal app |
Here is the output -
|
And with a full rust backtrace -
|
Looks that this may be fixed by image-rs/image#1417, but sadly I can't use git version of this library which have this issue fixed due build failures. The only way to see this fixed is to wait for new official version. You can also select all possible file extensions inside |
Currently Czawka 2.4.0 disabled such extensions, so for now this crashes should not be visible. |
This is fixed in Czkawka master branch. |
Running from master (after 2.3.2), I am seeing a hang near the end of image processing. It hangs most of the way through and doesn't seem to be doing any processing. I was seeing the same issue with 2.3 and upgraded to HEAD to see if that resolved the issue.
The lsof & strace reports no open images and seemingly an 'Resource temporarily unavailable' issue. Is there some way progress is lost when an issue pops up?
Current stage - 100%
All stages - 100%
Hashing 448883/449109 image
The text was updated successfully, but these errors were encountered: