> I also have a report of a memory leak in memory.c We use a well-known memory checker called valgrind. We included your loop but set it to 100 iterations and it returned
==26900== LEAK SUMMARY: ==26900== definitely lost: 0 bytes in 0 blocks. ==26900== possibly lost: 0 bytes in 0 blocks. In addition we looped for about 10 minutes and tracked memory usage and the process did not grow in memory usage as you experienced. IMDisplay is a contributed project and its possible it has a memory leak. If you can show there is a memory leak in MagickCore or Magick++ we are interested in getting the problem repaired. In the mean-time we have been unable to produce a memory leak. If you can provide additional information such that we can reproduce a leak, we will fix the problem immediately since leaks are a very high priority just under security fixes. _______________________________________________ Magick-bugs mailing list [email protected] http://studio.imagemagick.org/mailman/listinfo/magick-bugs
