On May 14, 2010, at 16:03 , [email protected] wrote:
> On Fri, May 14, 2010 at 3:26 PM, <[email protected]> wrote:
>> On Fri, May 14, 2010 at 2:43 PM, Brian Blais <[email protected]>
>> wrote:
>>> Hello,
>>>
>>> I have the following code, where I noticed a memory leak with +=,
>>> but
>>> not with + alone.
>>> import numpy
>>>
>>> m=numpy.matrix(numpy.ones((23,23)))
>>>
>>> for i in range(10000000):
>>> m+=0.0 # keeps growing in memory
>>> # m=m+0.0 # is stable in memory
>>>
>>>
> Maybe it's not a "true" memory leak, my python process eventually
> garbage collected the extra memory that was built up.
>
It crashed a simulator of mine (at least in Windows), until I figured
out the workaround, so I would consider it a leak. :) it certainly
shouldn't grow like that. if anything m=m+0.0 should chew of *more*
memory than m+=0.0.
bb
--
Brian Blais
[email protected]
http://web.bryant.edu/~bblais
http://bblais.blogspot.com/
_______________________________________________
NumPy-Discussion mailing list
[email protected]
http://mail.scipy.org/mailman/listinfo/numpy-discussion
