CPU load 70% - no progress for 6 hours

[Uwe]

Hello,
the process 'update' generates a CPU load of 70%, but according to the debug log nothing has happened for 6 hours. In addition, the log is full of error messages (see attachment).
 Is there anything I can do?
Best regards, Uwe

[Mario]

No error messages in this log file. But a ton of warnings.
But as you can see in the log file, IMatch has found many folders which are out of date (see IMatch 2025.1.2 release notes about why this happens).

I see many warnings from ExifTool "No such city in Geolocation database", which I have not seen before. I have posted a question on the ExifTool board. I know that ExifTool recently added support for a geolocation database based on a subset of GeoNames.org, but I decided not to use it due to it's limitations and the already existing support for GeoNames.org, HERE, and Google in IMatch.

Some warnings about unknown/broken maker notes, too larger arrays not being decoded (probably some metadata Lr or Ps havd written). All normal.

Error 3 placing xmpMM:HistoryAction in structure or list [x2] - N:\Katalog_Foto\01_Foto\2024\2024_06\2024_06_10\20240610_121620-000.png

Have not seen that before. Probably the PNG has some broken metadata section.

More unknown masker notes.

A warning from IMatch about a XMP region imported where it cannot detect a face. Can be an invalid region, or a face region written by a software which could detect a face in that region. Normal.

Some warnings about PDF files with unknown or unsupported fonts.

You can find all warnings by searching the log for W>.
A very unusual high number of warnings for your images, videos and other files.

The log runs from 19:12:04 to about 20:01:11.
Then IMatch seems to idle a bit, purging files from the cache (Which Cache settings do you use, which purging strategy have you  enabled).

Again some WIC error messages about unsupported formats.

Then warnings from the cache manager with Windows error 32 (cannot delete file locked by other application)?

More errors about broken PDF files or PDF files with unsupported features or form errors.

A lot of cache purging.

The log ends 08:17:39 next day.

Interesting it that, at some point, IMatch reports a memory usage of 12GB (on a 64GB machine, so no real problem). But that indicates that ExifTool, FFMPEG, PDFLib or WIC have consumed a lot of memory while processing some of your files. Which usually indicates a corrupted file or a bug in listed 3rd party helpers.

Of course every warning, every failed attempt to decode the large metadata chunks in your files (probably from Lr or Ps with the "record every pen stroke I do" option enabled), every locked file the cache manager cannot delete, every failed WIC call to decode a RAW file, every unsupported or broken PDF file, will show down the indexing process considerably. And this multiplies by the large number of files IMatch has to process.

Maybe just close IMatch, restart your PC, and let IMatch continue,
The Info & Activity Panel shows you how much work is left to do.