On 29.01.2014 20:44, Nathaniel Smith wrote: > On Wed, Jan 29, 2014 at 7:39 PM, Joseph McGlinchy <jmcglin...@esri.com> wrote: >> Upon further investigation, I do believe it is within the scipy code where >> there is a leak. I commented out my call to processBinaryImage(), which is >> all scipy code calls, and my memory usage remains flat with approximately a >> 1MB variation. Any ideas? > > I'd suggest continuing along this line, and keep chopping things out > until you have a minimal program that still shows the problem -- > that'll probably make it much clearer where the problem is actually > coming from... > > -n
depending on how long the program runs you can try running it under massif the valgrind memory usage proftool, that should give you a good clue where the source is. _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
