Program eating memory, but only on one machine? (Solved, sort of)

Robert Kern robert.kern at
Mon Jan 22 21:14:59 CET 2007

Per B.Sederberg wrote:
> Per B.Sederberg <persed <at>> writes:
>> I'll see if I can make a really small example program that eats up memory on
>> our cluster.  That way we'll have something easy to work with.
> Now this is weird.  I figured out the bug and it turned out that every time you
> call numpy.setmember1d in the latest stable release of numpy it was using up a
> ton of memory and never releasing it.

Hmm. With a recent checkout from SVN, I don't see any memory increase.

In [15]: from numpy import *

In [16]: ar1 = arange(1000000)

In [17]: ar2 = arange(3, 7)

In [18]: import itertools

In [19]: for i in itertools.count(1):
   ....:    if not i % 1000:
   ....:        print i
   ....:    x = setmember1d(ar1, ar2)

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

More information about the Python-list mailing list