Only recently I get a strange behaviour with calling the "histogram:" operator ....
convert sdim004.jpg histogram:histogram.gif
Gives me full CPU ocuppation (I have a dual core) so I get a single core occupied
The image is 2688x1792 8 bit JPG
The strange fact is that It works in the first two or 3 calls ... after that it completly locks the cpu ....

When it works correctly I get a 256x200 bits GIF ... But with a strange "larger" (7Mb or biiger) size .... ?!?
What am doing wrong ?
If I try to convert it into a new file using "irfanview" or other program get a 15kb gif image ...(?)
Any ideas ?
Edited:
Due to some further reading (usage web docs) I have found that the CPU lock and or the size is all related to the "comment" part of the histogram ...
so It is now small and fast ...

Thanks for the help ...
Edited:
Forgot to mention that sometimes it works correctly ....
and I am using the pre-compiled windows Q16 6.6.3-7 version ...