I'm using a clean install of 0.81 64bit for windows (win7).
I figured I'd use the 'add folders' in the catalog section of options and leave it running to add thumbs to the cache.
Only problem is XnViewMP eats ALL my memory and that 16Gig of RAM and a 8Gig page file! Windows shuts down
the desktop manager to add memory then kills XnView if that fails. It looks like there is limit to how many images and
directories can be added (unless more memory is added). Also once its got its greedy hands on this memory it wont give
it up unless I quit XnViewMP.
Is anyone else experiencing this?
Thanks
P.S. Despite this problem I have to say I'm really impressed with XnViewMP.
Cached Directiory - Add folders uses all my memory
Moderators: helmut, XnTriq, xnview
Re: Cached Directiory - Add folders uses all my memory
there is no folder limit. your folders contains only image files?
Pierre.
Re: Cached Directiory - Add folders uses all my memory
"there is no folder limit. your folders contains only image files?"
Just images files. Some folders contain desktop.ini files and small .txt files.
I did start off big at the top of directory structure (and that will include video files) but have downsized and added smaller directory groups of just images and experimented with differing quantities. I have found there is a limit to how many images can be cached in this way. I've also been watching the memory usage in Process Explorer and seen memory jump from 700Mb to over 4Gb then jump again to 20Gb. At this point if I let the program continue it will crash. I have also been experimenting with the 'show all files' recursive viewing of all images and seen a similar pattern in memory usage. It could be the 'add folders' just doing the same using the memory (for unseen thumbs).
Only bright point is if the program crashes none of the new cached images are lost.
Just images files. Some folders contain desktop.ini files and small .txt files.
I did start off big at the top of directory structure (and that will include video files) but have downsized and added smaller directory groups of just images and experimented with differing quantities. I have found there is a limit to how many images can be cached in this way. I've also been watching the memory usage in Process Explorer and seen memory jump from 700Mb to over 4Gb then jump again to 20Gb. At this point if I let the program continue it will crash. I have also been experimenting with the 'show all files' recursive viewing of all images and seen a similar pattern in memory usage. It could be the 'add folders' just doing the same using the memory (for unseen thumbs).
Only bright point is if the program crashes none of the new cached images are lost.
Re: Cached Directiory - Add folders uses all my memory
so you have tried with only image files in folders, right?
how many image files do you have? which format?
I'll try to reproduce...
how many image files do you have? which format?
I'll try to reproduce...
Pierre.
Re: Cached Directiory - Add folders uses all my memory
Thanks for your prompt replies Pierre.
I think I might have a reason for the memory spike - EXIF!. I have been doing some more experimenting. I have older family photos scanned years ago that have no EXIF metadata and newer photos from digital camera filled with EXIF data - all images jpg format. When I added these images (about 40,000) the memory usage did rise gradually but then it spiked again. I aborted the operation and when I checked the folders to see where the cataloging got to, it had just started on the new images with the EXIF data. The previous folders I tried to add, when I first had this problem also were images packed with EXIF data.
I think I might have a reason for the memory spike - EXIF!. I have been doing some more experimenting. I have older family photos scanned years ago that have no EXIF metadata and newer photos from digital camera filled with EXIF data - all images jpg format. When I added these images (about 40,000) the memory usage did rise gradually but then it spiked again. I aborted the operation and when I checked the folders to see where the cataloging got to, it had just started on the new images with the EXIF data. The previous folders I tried to add, when I first had this problem also were images packed with EXIF data.