Similarity Forum

General Category => Bugs => Topic started by: Roy on August 10, 2013, 06:10:06

Title: Similarity leaking memory
Post by: Roy on August 10, 2013, 06:10:06
I am using build 1694 64bit on windows when i try to do an image comparison the memory is maxing out quickly after only about 50 images.  I am also seeing large numbers of decoder.exe and even after shutting down the app I can only get the memory back with a reboot (I haven't tried killing all the decoders individually).  any ideas?
Title: Re: Similarity leaking memory
Post by: Admin on August 15, 2013, 20:17:14
What size of your images ? And how many cpu cores do you have ?
Title: Re: Similarity leaking memory
Post by: rehull on August 26, 2013, 01:10:47
I have 8 cores and the images are 3-400 MB
Title: Re: Similarity leaking memory
Post by: Admin on August 31, 2013, 00:38:47
How many memory do you have (RAM) ?
Try decrease work threads in Options to 4 or 6 threads.
Title: Re: Similarity leaking memory
Post by: rehull on September 03, 2013, 05:26:25
I have 16 GB of RAM

I will try reducing the threads
Title: Re: Similarity leaking memory
Post by: rehull on September 22, 2013, 23:41:52
I tried 6 and 4 threads and i still ran out of memory
I have been running 1 thread for about 5 hours and it looks all right
Title: Re: Similarity leaking memory
Post by: Admin on September 27, 2013, 00:56:50
We think problem in 400Mb images, if they decoded and processed they can consume more memory, what format what files ? (*.raw). In next release we limit processing files to 100Mb maximum.
Can you also send us all logs from "%appdata%\Similarity" folder ?