Page 1 of 1

Image Comparer 3.8 hangs in windows 7

Posted: Mon Sep 12, 2011 4:32 pm
by Martin Hansen
I have bin using IC3.8 for some time on my old machine running XP and generaly it has never hanged.
But after i got my new machine running windows 7 it hangs almost every time it is running the comparing part.
The program dosent shutdown but will hang until I manualy shut down the process.

It is ONLY when comparing that the program hangs.
It happens at different times in the comparing process
It happens especially fast if I'm working in another program or just tabs away from IC.

I have already tried the following:
1: Enabled the one cpu limitation in the program.
2: Run IC with higher/lower priority.
2: Run IC in XP SP2 compatibility mode.
3: Run IC as administrator.


If i can deliver some kind of debug information then just ask.

Martin Hansen

Posted: Thu Sep 15, 2011 1:30 pm
by Gemini
You could try the previous version, will it behave the same way?
Download it here


3.7 Works fine!!

Posted: Sat Sep 17, 2011 4:15 pm
by Martin Hansen
Down grading to image compare 3.7 removed the problem.

I also detected that the 3.8 Image Comparer had a strange error while comparing.

I had created a gallery with 5517 images in.
But when comparing the image counter was showing 15196 images to compare in the small comparing window.

I did not notice it before. I thought it was the number of singles comparing's it was counting.

Posted: Sun Sep 18, 2011 8:53 pm
by Martin Hansen

I tested both the 3.7 and 3.8 on the win 7 and xp machine.
I found 2 general problems:
The freezing always happens when running with the "not in same dir" option.
event when there was no freezing the count up in the compare window was very choppy.
Disabling the multi core CPU helps on the xp machine.
It makes the comparing slower but the count up is now smooth again.
Disabling the multi core cpu DOES NOT help on the window 7 machine.
And looking on the windows task manager the program was still running on all the cores and all hyper threads (12 in all).
Forcing the program to run on 1 CPU thread makes it run smooth again but extremely slow ( 1 CPU on old xp 18,20 min win 7 estimate 2.4 hour )

There is clearly some problem with multi processor and the "not in same dir option"

The 3.7 had the same problems as the 3.8 just without the freezing.

best regards Martin Hansen

Posted: Fri Sep 23, 2011 8:36 am
by Gemini
Thank you Martin Hansen so much for the detailed description of the problem - hopefully, it will help us fix the bug.


Posted: Sat Nov 24, 2012 8:37 pm
by gavind
Can anyone please confirm if this issue is already fixed with the latest version?