Error messages in log

Started by lama, August 29, 2024, 10:52:29 AM

Previous topic - Next topic

lama

I'm adding some more folders to the database and got the message while shutting down "there are errors in the log file" (don't remember the original text).

I found a lot of these exceptions:

08.28 15:54:58+   32 [3BA4] 01  W> Exception [88982f50]  'V:\develop\IMatch5\src\ptpif\ptd2d.cpp(240)'
08.28 15:54:58+    0 [3BA4] 01  W> Failed to load image with PTD2D. 88982F50 - Die Komponente wurde nicht gefunden.  'V:\develop\IMatch5\src\ptpicore\PlugIns\ptpipip\PTPIImage.cpp(494)'
08.28 15:54:58+    0 [3BA8] 01  W> Exception [88982f50]  'V:\develop\IMatch5\src\ptpif\ptd2d.cpp(240)'
08.28 15:54:58+    0 [171C] 01  W> Exception [88982f50]  'V:\develop\IMatch5\src\ptpif\ptd2d.cpp(240)'
08.28 15:54:58+    0 [3BA8] 01  W> Failed to load image with PTD2D. 88982F50 - Die Komponente wurde nicht gefunden.  'V:\develop\IMatch5\src\ptpicore\PlugIns\ptpipip\PTPIImage.cpp(494)'

I don't know if they are serious problems.

Also some minor warnings, which I think are not important:
Warning: [minor] Unrecognized MakerNotes - E:\BILDER\digi-foto\2021\08\12\IMG_20210812_161453.jpg

The log file has 12 MB, so I don't know if I should attach it here.



Mario

I see no errors (which use the E> indicator), just some warnings.

Windows WIC failed to load/recognize some of the files you are processing (I cannot see the file names).

ExifTool reports a warning about unrecognized/corrupted make notes in the IMG_20210812_161453 .jpg file.
This is a very common problem. Many applications out there are not aware of EXIF maker notes and damage then when re-saving the image. EXIF maker notes often contain offsets (pointers to specific bytes in the file) and when an application re-saves an image, changing it's size and structure, without either stripping the maker notes or updating the byte offsets, all or parts of the maker notes are corrupted.

If IMatch reports that an error has been logged, the log file must contain a line with E> somewhere.
Have you considered ZIPping the log file? This reduces it by about 80% and allows you to attach it.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

lama

At the end of the log are a lot of these:
E> ...  'V:\develop\IMatch5\src\IMEngine\IMCacheManager.cpp(374)'

I zipped the log (could have thought about this by myself ...)

Mario

Geez. This log reports:

27677 warnings.
2295 errors.

That's quite a lot!

All the errors are logged by the IMatch cache manager, when it tries to load images in the background.
But there are literally tons of these exceptions. Were you using the Viewer?
There are about as many E> logged as there are exceptions thrown by Windows WIC. It looks like Windows WIC crashed badly while processing images.

But I see only JPG file names in the log, and JPG files are loaded by IMatch internal routines, not via WIC. IMatch loads cache images in JPG format via WIC, because this is faster with DirectX and graphic cards.
Were you processing RAW files?

Tip: Switch IMatch to debug logging via Help menu > Support while diagnosing this. This produces more detailed log files with file names logged, too.

I see a ton of ExifTool reports about corrupted maker notes. These JPG files are probably in real bad shape, metadata-wise. Maybe this is what causes Windows WIC to crash / fail with every image? Impossible to tell without having some of these images here. 

Are these JPG straight from the camera or have you processed these JPG files with something?
Because I have never seen this large number of ExifTool warnings about corrupted maker notes. Which software created this problem?

Maybe try this:

1. Reboot your PC.
2. To rule out that the problems are caused by Windows WIC, open Edit menu > Preferences > Application.
Enable the "Prefer photools.com RAW Processing" option.
IMatch now processes RAW files with LibRaw instead of Windows WIC.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

lama

I see 12 Warning: Error rebuilding maker notes (may be corrupt):

8 are stills from a cheap action cam, 4 are panoramas made with Olympus Viewer.

The multiple warnings "Unrecognized MakerNotes" are from Huawei VOG-L29 phone, maybe also from other phones.

W> ETWARN:Warning: [minor] Error reading PreviewImage from file - E:\BILDER\digi-foto\2024\07 Bretagne\07\M1275127-ORF-011.jpg: These *-ORF-*.jpg are from DXO PureRaw 4. Each of these has also a ORF-File, from where they are produced.

I will make what you suggest and import some more folders.


Mario


QuoteThe multiple warnings "Unrecognized MakerNotes" are from Huawei VOG-L29 phone, maybe also from other phones.
maybe help the ExifTool project by providing some sample images via they forum: https://exiftool.org/forum/
Maybe Phil can add support for the maker notes produced by this phone.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

lama

After importing a new folder, I cannot find any W> or E> in the debug-log.

So all these errors are generated from some "special" jpgs?

I enabled the "Prefer photools.com RAW Processing" option. Should I stay with this? My new camera is an Olympus EM1Mk3 (which my Lightroom v.6 doesn't accept) and maybe is not supported by WIC.

I just saw your new message helping ExifTool, I will do this.

Mario

No harm in using LibRaw, if your RAW formats are supported.
You can run WIC Diagnostics (Help menu > Support) for one of the new ORF files to see if WIC and/or LibRaw support the file format.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

lama

Thanks a lot for your support!