Crash When Processing Multiple Files

[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.

[fincire]

Thank you for your reply, Mario! 

• The app is installed correctly (I think) -- this problem is new with the latest version of Imatch, but the databases I'm working with are also new so the fact that it's Imatch 2025 might not actually be relevant.
• What's freezeem\app.json? Is it an Imatch file, or something unfamiliar to you? If it's important for Imatch, what should I do--just reinstall the entire application?
• While I'm pretty sure I've set up exceptions in BitDefender and Malwarebytes for all of Imatch's moving parts, it's certainly possible I neglected something. I will double-check.

The system isn't working too hard during these instances; in fact I've tried terminating everything and just running a big folder rescan or delete-rejected and the freeze still occurs.

The User Abort you saw in the log was likely my killing Imatch from Task Manager. I hit cancel on whatever file operation I'm trying and the popup just grays out, so killing the task and restarting it is the only option.

The PC is a Core i7 7700K with 32GB of memory and a 6GB GeForce RTX 2060. Imatch itself is on my main system drive, which is a PCI-x 3 nVME SSD; the database and the actual image files are each on their own SATA SSDs. It's not top of the line any more, but not ancient; as you say, it should be more than enough to handle everything.

ANYWAY, I appreciate your response and will get back with more info once I have a chance to do some experiments.

[thrinn]

What's freezeem\app.json? Is it an Imatch file, or something unfamiliar to you? If it's important for Imatch, what should I do--just reinstall the entire application?

As I don't see this App in my installation, it is most likely non-standard, that is, some user-created app. If it is not one of your owns, I found a post from 2017 (!) where ubacher shared an App with this name - see https://www.photools.com/community/index.php/topic,6787.msg46926.html#msg46926.

Maybe you installed this app in the past? If you don't need it anymore, you can delete the entire App folder ( C:\ProgramData\photools.com\IMatch6\webroot\user\freezeem )

[Mario]

What's freezeem\app.json? 

Not a standard IMatch app. Delete the entire folder when you are not using it.

The User Abort you saw in the log was likely my killing Imatch from Task Manager.

No. This is logged when the user aborts some operation in IMatch.
When you terminate IMatch via Task Manager, it has no chance to log anything.

As I said above, the most likely culprit is your virus checker interfering. We've had issues with Bit Defender in the past.