Crash When Processing Multiple Files

Started by fincire, Today at 06:16:00 AM

Previous topic - Next topic

fincire

Imatch seems to freeze when conducting operations on large folders or groups of files. I've observed this with various commands, particularly Delete Rejected Files and Rescan <Folder>. According to Task Manager, Imatch stops responding (for example, during a Delete Rejected process). There's some CPU activity, but it's usually around 0.2%. I've left it open for more than an hour just to see, and it doesn't seem to recover; eventually I terminate Imatch from Task Manager and restart it.

I've followed all of Mario's usual performance suggestions, such as keeping the app and database on separate SSD drives and making sure to exclude Imatch from virus/security software. 

It seems doubtful this is a bug, so maybe it's an issue with my database. I've attached my most recent log file and would welcome any insight. Thank you!

Mario

The log file ends with an 10010 error/warning: "User Abort".

But the database has only 17,000 files, but IMatch takes a whooping 30 seconds to load this small database and over a minute (!) to initialize the user interface. This is way to slow.

The system reports 4 processor cores and 32GB RAM, which should be plenty.
75% of the available RAM are already used when IMatch starts, which indicates that some memory-hungry applications are running already.

IMatch reports an error with this custom app:

AppManager::Error parsing file 'C:\ProgramData\photools.com\IMatch6\webroot\user\freezeem\app.json': 'default document does not exist.'

Please check that the app is installed properly and contains all the default files (index.html).

Judging by the super-slow load speed, my guess would be that a virus checker or something else is interfering. Or that the system is super-busy, not allowing IMatch to load the database quicker. All file-system operations are extremely slow.

Try making an "exception" for the folder containing the database and the IMatch2025x64.exe executable and see if this changes anything. IMatch being blocked forever during a file system operation is a typical sign of a virus checker misbehaving.

ubacher

Just want to report that I also have found unusual long delays when Delete Rejected Files and Rescan <Folder>.


Mario

Quote from: ubacher on Today at 10:49:07 AMJust want to report that I also have found unusual long delays when Delete Rejected Files and Rescan <Folder>.


And you have kept the log files to provide a minimum of details for your post?
Or was this from a thread you remember but I don't?

Deleting a file can perform very differently, depending on factors like local or remote file, the structure of the database, the amount of data to remove from the database, the number of categories in the database and many other factors.

It takes about twice as long to delete a file from my one million file test database than it takes for a smaller 100,000 files test database.

ubacher

My report is based on experience on using Imatch heavily (and for many years).
My inspection of the log file did not show a clear reason.

Previous experience with upgrades tells me that it takes a few months for these kinds of problems to
get corrected. It seems mostly when other problems are corrected such slowdowns/hangups disappear also.

After the previous update I swore that next time I would wait a few months before I upgrade the next time.
But the new PEEK feature and the handling of dng V1.7 files made me update right away!