Dear all, I can confirm the problem; I had been holding back on reporting it, assuming it was a problem in my code, and planning to look into it further. I can provide my script that uses the function and exhibits the memory leak tomorrow.
Greetings, Yung-Chin On Nov 15, 2007 12:46 PM, Douglas McNeil <[EMAIL PROTECTED]> wrote: > > > python 2.4.4; numpy-1.0rc1; gsl-1.8. > > With pygsl 0.9.0 (0.9.1 fails to compile for me as well) I find a serious > memory leak when using the odeiv evolve. > > For example, after changing the example in help(pygsl.odeiv) so that it > works -- i.e. fixing the complaints about the number of parameters f takes > and the fact that the returned y isn't (a numpy nd.array of) [1.0,2.0,3.0] > but [[1.0,2.0,3.0]] instead -- it burns through memory rapidly. > > I don't know if the unexpected change in y's depth is a sign of what the > problem is or not. > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > pygsl-discuss mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/pygsl-discuss > -- Yung-Chin Oei Clare Hall, Cambridge CB3 9AL Mobile: +44 7757 183115 Dept of Physics, Cavendish Laboratory University of Cambridge www.bss.phy.cam.ac.uk ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ pygsl-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pygsl-discuss
