App freezes if I leave it running in the background to scan directories (v1.5.5)

leonardoa

This seems to have happening all the time.

I have the latest version of the app (1.5.5) installed on my Windows 11 laptop (Lenovo Thinkpad X1 Extreme Gen 2 with 16Gb RAM).

My photo collection is on a 3Tb external drive connected via USB3 port. The photo collection is around 2Tb in size (going as far back as year 2000).

I installed the app a few days ago and the the app is still scanning my folders but wheneve I leave the app running in the background while I use my laptop, each time I went back to the app to see the progress it won’t be freezing. Clicking inside the app window doesn’t do anything. Moving the mouse over the menu bar at the top or the status bar at the bottom of the app windows, the mouse cursor changes to spinning wheel. The status bar shows the last known image being scanned and it just seem to stuck there at some random image.

Most of my photos are JPGs and more recent some are DNGs, and some MP4s, but it seems to hang at some random place, and not at particular file type.

Any ideas?

Andrey

leonardoa I am sorry this is happening. It is really hard to say what is causing this, it does not seem to be common problem. I think we can use debug logging to find out if there any errors during processing: https://community.tonfotos.com/d/26-making-debug-logs-in-tonfotos

leonardoa

I turned on debug logging and have been running the app in the background since yesterday and it has not once frozen!
It’s still chugging along inside my folders and importing the photos. Another 36 hours to go, according to the app.

I noticed that it’s really slow (around 5 secs per image) when scanning a .NEF (Nikon RAW format) file compared to JPG. Any reason for it or is it just the file size? This means, it can scan only 720 NEF images per hour.

Andrey

leonardoa I am glad that this logging worked like some sort of workaround, but please keep checking free space on your system drive as there are tons of logs gets written, you can run out of space pretty fast. This is not intended to be used all the time, this is only for debugging.

As for .NEF, yes, size defintely contributes to that, but also we use separate library to process RAW files (libraw), and it is not as fast as some other imaging libraries, but it has best possible compatibility with cameras.