[Numpy-discussion] Memory leak in signal.convolve2d? Alternative?
Tue Mar 9 15:32:56 CST 2010
On Tue, Mar 9, 2010 at 4:24 PM, David Reichert
> Hm, upgrading scipy from 0.7.0 to 0.7.1 didn't do the trick for me (still
> running numpy 1.3.0).
> I'm not sure if I feel confident enough to use developer versions, but I'll
> look into it.
If you don't need the extra options, you could also use in the
meantime the nd version signal.convolve
or the fft version signal.fftconvolve
> On Tue, Mar 9, 2010 at 7:57 PM, Robert Kern <firstname.lastname@example.org> wrote:
>> On Tue, Mar 9, 2010 at 13:49, David Reichert <email@example.com>
>> > Hi,
>> > I just reported a memory leak with matrices, and I might have found
>> > another (unrelated) one in the convolve2d function:
>> > import scipy.signal
>> > from numpy import ones
>> > while True:
>> > scipy.signal.convolve2d(ones((1,1)), ones((1,1)))
>> This does not leak for me using SVN versions of numpy and scipy. I
>> recommend upgrading.
>> Robert Kern
>> "I have come to believe that the whole world is an enigma, a harmless
>> enigma that is made terrible by our own mad attempt to interpret it as
>> though it had an underlying truth."
>> -- Umberto Eco
>> NumPy-Discussion mailing list
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion