On Sun, May 22, 2011 at 2:54 PM, Jeffrey Spencer <[email protected]>wrote:
> Sorry. I attached here the class and script to run it. It is just a > minimalistic example of what I'm really doing that exhibits the same > behavior. All the script does is run at.createSpecific after instantiating > the class. I have seen this exhibited on many other cases but it runs fine > in Windows XP. Here is what the script does: > > import MemoryLeak > at = MemoryLeak.Model() > at.createSpecific() > > That manages to eat up all my cpu cycles for about 5 minutes, but no leak (on OS X). I also don't see anything in the code that can potentially give problems. I suggest you strip this down a lot more so you can isolate the problem. If in your original code you were making a lot of figures in one of those for loops without explicitly closing them, that could perhaps be a problem. But you removed all I/O and matplotlib related code already (except for imports and some keywords). Ralf
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
