Thanks for all the answers, they were helpful!
I was using 1.7.0 and now installed from git:
https://github.com/numpy/numpy/archive/master.zip
And it looks like the memory leak is gone, so I guess I was hitting that
known memory leak bug. Thanks!
-Jaakko
On 02/26/2013 09:04 AM, Nathaniel Smith
Is this with 1.7? There see a few memory leak fixes in 1.7, so if you
aren't using that you should try it to be sure. And if you are using it,
then there is one known memory leak bug in 1.7 that you might want to check
whether you're hitting:
https://github.com/numpy/numpy/issues/2969
-n
On 25 Feb
Josef's suggestion is the first thing I'd try.
Are you doing any of this in C ? It is easy to end up duplicating memory
that you need to Py_DECREF .
In the C debugger you should be able to monitor the ref count of your
python objects.
btw, for manual tracking of reference counts you can do,
sy
On Mon, Feb 25, 2013 at 8:41 AM, Jaakko Luttinen
wrote:
> Hi!
>
> I was wondering if anyone could help me in finding a memory leak problem
> with NumPy. My project is quite massive and I haven't been able to
> construct a simple example which would reproduce the problem..
>
> I have an iterative a
I added allocation tracking tools to numpy for exactly this reason.
They are not very well documented, but you can see how to use them
here:
https://github.com/numpy/numpy/tree/master/tools/allocation_tracking
Ray
On Mon, Feb 25, 2013 at 8:41 AM, Jaakko Luttinen
wrote:
> Hi!
>
> I was wonderi
Hi!
I was wondering if anyone could help me in finding a memory leak problem
with NumPy. My project is quite massive and I haven't been able to
construct a simple example which would reproduce the problem..
I have an iterative algorithm which should not increase the memory usage
as the iteration
