My user appdata local temp folder is being filled up causing my 500GB m.2 drive to be completely full and then cause imatch and other applications to crash.
When I close all applications and delete everything in this folder I have plenty of space for a while and then the temp folder causes the C drive to get full.
One of the consequences is that imatch has to update images every day which starts of telling me it's going to take days but then settles down to a much shorter time.
I have spent some trying to identify which application is causing the problem and since installing and running Process Monitor suspect that imatch is guilty, see screen grab attached.
I also attach log file
When I look at the log, the first thing I see:
Cache folder A:\imatch cache not found. Fall-back to C:\Users\Stefan\AppData\Local\Temp\
Please check that the cache folder you have configured actually exists. Edit menu > Preferences > Cache.
This is a hard error and IMatch will tell you when you close it that an error has been written to the log file.
Did you see the message and looked at the log file?
I shall add yet another app health message to inform users when they delete or take offline the cache folder they have configured. A: is quite unusual, too.
Also: Relocation source C:\Data\Current Photos\ not found in database.
Your Edit > Preferences > Database Portability options seem to be out of order.
Quite a number of warnings about unsupported files or failures to process files.
For example: Error loading E:\Photos\Photos Prior ..._1020026.JPG with error 1 'Empty input file'
or
Error loading E:\Photos\Photos Prior Years\...¦\SJS_131128_0049.CR2
There seems to be a | pipe character in the file name, not sure? This is not permitted on Windows?
Search the log for lines containing W> and E> to find all errors and warnings logged.
Quote from: Mario on February 17, 2025, 06:29:26 PMCache folder A:\imatch cache not found. Fall-back to C:\Users\Stefan\AppData\Local\Temp\
Brilliant, solved my problem. I'd moved imatch databases, cache and image files to a dedicated 4TB m.2 ssd on E:. I think I assumed that the cache was created on the same drive as the database. My error!!!!
QuoteDid you see the message and looked at the log file?
Sorry, answer is no to both questions
QuoteAlso: Relocation source C:\Data\Current Photos\ not found in database.
Your Edit > Preferences > Database Portability options seem to be out of order.
Thanks, I've corrected this
QuoteThere seems to be a | pipe character in the file name, not sure? This is not permitted on Windows?
I have been using the folder format YYYY\YYYY-MM-DD ¦ Description for some time using renamer to create the folders. Works really well for me and I haven't encountered any issues.
QuoteSearch the log for lines containing W> and E> to find all errors and warnings logged.
I haven't previously understood how to search the help file. This advice is very helpful. I have been using W> and E> to find issues and cleared the majority of them. There are a few remaining which I don't understand but will research these further and if necessary raise in a separate post. I've also been using the dashboard and cleared most of the issues just 39 writing metadata problems and 1 exif error to resolve!
Thanks once again Mario for the outstanding support!
Very good.
In case another runs into the same issue, I have added a new error message displayed to the user prominently when the configured cache folder does not exist and cannot be created.
IMatch separates the cache folder from the database location to enable users to use a large and maybe slower (spinning) disk to hold the cache, while keeping the database on the fastest SSDs. Especially notebooks / laptops often have smallish internal SSDs and keeping the cache on an external disk or a SD-card conserves precious space on the SSD.