Thumbnails missing

[Ted]

I'm using the Trial version for now, but it has a problem that I've seen for years on previous versions, and I guess I've come to expect it - after scanning thousands of new files, 'some' of the thumbnails are missing.  I'm having to manually go through and find and 'force update' each file to get the thumbnail rebuilt.  Most, but not all of them are NEF, DNG, PSD, TIF.  Is there a way to use the filter and display only those images with no thumbnails?  It would make it easier to rebuild them.

Thanks.

[Mario]

Did you check the log file for W> or E> lines? Usually when IMatch is unable to extract a thumbnail, the file format is not supported. Or maybe there was  race condition in the image library, a temporary stress issue with the WIC subsystem in Windows (you mentioned added thousands of files).

I usually create test databases with 10K, 30K, 50K files during each test session and so far I did not experience this.

Tip: You may be able to find the files in question by using the Orientation & Dimension filter. I assume that the width/height of these files reported by IMatch is 0? In that case you can find them easily using the filter panel and "As specified" and 0 to 10 for horizontal/vertical to find all files < 10 pixel.

[Ted]

I did not look at the log, however, during the initial processing of 200K+ files I did run into 'low memory' problems several times and had to restart.  I keep running the database diags and compression but have not found any errors there.

As for the file format not being supported - these are the same file formats I've been processing 5.8.? for a long time, and it would seem to me that it's too random for that - and it processes them correctly when I do a 'force update'.  I suspect a stress problem as you put it.

Many, but not all of the files are 0x0 and I have used that to help find them.

Thanks - I'll just keep looking.  Frustrated!

[Mario]

Adding 200,000 files in one go is a recipe for trouble. This is putting IMatch, all 3rd party libraries, Windows WIC, the memory manager etc. under prolonged stress. Which is not a problem per-sé but can cause tiny problems to become big problems.

IMatch does not need much memory when indexing files. It processes multiple files simultaneously, but even if this means that all 4 (usually) threads load an image at the same time, this needs maybe a few hundred megabytes - even if you work with 64MP or larger files.

If you see an out-of-memory message, something went wrong.  Either you are processing super-large files. Or maybe PDF documents? Some PDF files crash Acrobat Reader, but only after using several gigabytes of memory. Or maybe there was an image that caused Windows WIC to allocate a few gigabytes of memory....

no way to tell without a log file copied right after the memory warning was shown. The log file would show us which files were processed last, how the memory allocation was etc.