Per B.Sederberg wrote:
> Per B.Sederberg princeton.edu> 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
> y
Per B.Sederberg princeton.edu> 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 lat
I had a similar problem with an extension module on Solaris years ago.
My problem at that time:
I requested memory and released it and requested more memory in the next step
and so on.
The reason that the memory was eaten up:
An answer out of this group was that the operating system doesn't releas
Wolfgang Draxinger darkstargames.de> writes:
>
> > So, does anyone have any suggestions for how I can debug this
> > problem?
>
> Have a look at the version numbers of the GCC used. Probably
> something in your C code fails if it interacts with GCC 3.x.x.
> It's hardly Python eating memory, thi
Per B. Sederberg wrote:
> Python 2.4.4c1 (#2, Oct 11 2006, 20:00:03)
> [GCC 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)] on
> [linux2 Type "help", "copyright", "credits" or "license" for
> more information.
Doesn't eat up.
> Python 2.4.3 (#1, Apr 7 2006, 10:54:33)
> [GCC 4.0.1 (Apple C
Hi Everybody:
I'm having a difficult time figuring out a a memory use problem. I
have a python program that makes use of numpy and also calls a small C
module I wrote because part of the simulation needed to loop and I got
a massive speedup by putting that loop in C. I'm basically
manipulating a
