Memory leak when searching IPTC data
Moderators: XnTriq, helmut, xnview
Memory leak when searching IPTC data
I've observered what looks like a memory leak when searching IPTC keywords. This occurs on a Win XP machine with 256MB physical memory. When I search a hierarchical set of directories containing about 25,000 images and 60GB in size, the XNVIEW memory consumption goes through the max VM limit within two minutes. My machine locks up and I have to reboot to recover.
This was on an IPTC keyword search that would have matched about 200 images. I am using version 1.80.3 on WinXP with all recent patches.
Otherwise this seems like a fine program and is very enjoyable to use and useful. Good work !
This was on an IPTC keyword search that would have matched about 200 images. I am using version 1.80.3 on WinXP with all recent patches.
Otherwise this seems like a fine program and is very enjoyable to use and useful. Good work !
Re: Memory leak when searching IPTC data
Strange i have no problem, you have IPTC on each file?thielges wrote:I've observered what looks like a memory leak when searching IPTC keywords. This occurs on a Win XP machine with 256MB physical memory. When I search a hierarchical set of directories containing about 25,000 images and 60GB in size, the XNVIEW memory consumption goes through the max VM limit within two minutes. My machine locks up and I have to reboot to recover.
This was on an IPTC keyword search that would have matched about 200 images. I am using version 1.80.3 on WinXP with all recent patches.
Otherwise this seems like a fine program and is very enjoyable to use and useful. Good work !
Pierre.
I should have mentioned that of the 25000 image files I was searching that only about 3000 have IPTC information (yet). I am in the process of using xnview to add keywords to my images and am only about 15% complete.
So when I had the memory consumption problem xnview was searching a combination of .jpg files directly as created by my camera, .jpg files processed by xnview (lossless rotate and IPTC keyword addition) , thumbnails created by easyThumbnails, and a few .mov files mixed in.
By the way, the options that are provided for IPTC keyword annotation are excellent - they make it very easy to annotate large sets of files with common and overlapping keywords. It is this ease of use that has motivated me to add keywords to my archive.
I don't have access to the machine that I observed this problem on right now but in about 5 hours I will try searching on directories with 100% IPTC annotation versus 0% IPTC annotation to see whether there is a difference.
Bart
So when I had the memory consumption problem xnview was searching a combination of .jpg files directly as created by my camera, .jpg files processed by xnview (lossless rotate and IPTC keyword addition) , thumbnails created by easyThumbnails, and a few .mov files mixed in.
By the way, the options that are provided for IPTC keyword annotation are excellent - they make it very easy to annotate large sets of files with common and overlapping keywords. It is this ease of use that has motivated me to add keywords to my archive.
I don't have access to the machine that I observed this problem on right now but in about 5 hours I will try searching on directories with 100% IPTC annotation versus 0% IPTC annotation to see whether there is a difference.
Bart
I cannot recreate problem on Win2k (512Meg RAM) 16000 files. 3482 search keyword results. I added "this is a test" for keyword on most of those files.thielges wrote: I don't have access to the machine that I observed this problem on right now but in about 5 hours I will try searching on directories with 100% IPTC annotation versus 0% IPTC annotation to see whether there is a difference.
I've got some more clues to isolate this problem. Of all of the files in my image archive it looks like the .MRW files (forgot about those !) which are the raw output from my camera (Minolta A2) create. I've uploaded an example of a MRW file that causes this problem on my computer to
<a href="http://thielges.members.sonic.net/xnview/">this directory</a> which contains <a href="http://thielges.members.sonic.net/xnvie ... .MRW">this MRW image</a>
Here's a screen shot of what the CPU and virtual memory usage looks like when I replicate the above MRW file 5 times and then do an IPTC search for a keyword :
<img src="http://thielges.members.sonic.net/xnview/perfmeter.GIF"/>[/img http://thielges.members.sonic.net/xnview/perfmeter.GIF]
<a href="http://thielges.members.sonic.net/xnview/">this directory</a> which contains <a href="http://thielges.members.sonic.net/xnvie ... .MRW">this MRW image</a>
Here's a screen shot of what the CPU and virtual memory usage looks like when I replicate the above MRW file 5 times and then do an IPTC search for a keyword :
<img src="http://thielges.members.sonic.net/xnview/perfmeter.GIF"/>[/img http://thielges.members.sonic.net/xnview/perfmeter.GIF]
When you search in a folder with this MRW, you have a leak??thielges wrote:I've got some more clues to isolate this problem. Of all of the files in my image archive it looks like the .MRW files (forgot about those !) which are the raw output from my camera (Minolta A2) create. I've uploaded an example of a MRW file that causes this problem on my computer to
<a href="http://thielges.members.sonic.net/xnview/">this directory</a> which contains <a href="http://thielges.members.sonic.net/xnvie ... .MRW">this MRW image</a>
Here's a screen shot of what the CPU and virtual memory usage looks like when I replicate the above MRW file 5 times and then do an IPTC search for a keyword :
<img src="http://thielges.members.sonic.net/xnview/perfmeter.GIF"/>[/img http://thielges.members.sonic.net/xnview/perfmeter.GIF]
Pierre.
Yes, when I create a folder containing 5 copies of that MRW file and then search that directory then I see the leak behavior. Here's another attempt of posting the WinXP perfmeter screen shot of what it looks like on memory consumption when I do that experiment twice :When you search in a folder with this MRW, you have a leak??
Are you able to download the .MRW file ? If not I can try to get a copy of it to you some other way. It is about 12MB in size.
mem leak fixed in 1.82
I have confirmed that the memory leak problem is gone with my original 25,000 images and 60GB search when using 1.82. We can consider this case closed.
Thanks !
Thanks !