This still occurs in numpy 1.0.3.1 so must have been fixed between that and your 1.0.4-5 version.
By the way the memory problem crashes my Intel Mac Book Pro (system 10.4.11) with the gray screen and black dialog box telling me to restart my computer. A very UN-unix like and UN-Mac like way of handling a memory problem IMHO. Let us Mac people not be too smug. -- Lou Pecora --- Alexandre Fayolle <[EMAIL PROTECTED]> wrote: > On Tue, Jan 29, 2008 at 02:58:15PM +0100, Oriol > Vendrell wrote: > > Hi all, > > > > I've noticed something that looks like an odd > behaviour in array.argsort(). > > > > > > # test1 --------------------- > > from numpy import array > > while True: > > a=array([8.0,7.0,6.0,5.0,4.0,2.0]) > > i=a.argsort() > > # --------------------------- > > > > # test2 --------------------- > > from numpy import array > > a=array([8.0,7.0,6.0,5.0,4.0,2.0]) > > while True: > > i=a.argsort() > > # --------------------------- > > > > > > test1 runs out of memory after a few minutes, it > seems that in each cycle > > some memory is allocated and never returned back. > > test2 runs fine until killed. > > > > I'm unsure if I'm missing something or if this > could be a bug. I'm using > > numpy 1.0.1 with python 2.4.4 in a debian stable > system. > > Certainly a bug, but it has been fixed and I cannot > reproduce in debian > sid (using 1.0.4-5) > > -- > Alexandre Fayolle ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion