[Numpy-discussion] ENH: Type specific binary search functions for `searchsorted`

2014-01-29 Thread Jaime Fernández del Río
Hi, I have just added a new PR: https://github.com/numpy/numpy/pull/4244 >From the commit message: This PR replaces the generic binary search functions used by `searchsorted` with type specific ones for numeric types. This results in a speed-up of calls to `searchsorted` which is highly dependen

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Joseph McGlinchy
Unfortunately I do not have Linux or much time to invest in researching and learning an alternative to Valgrind :/ My current workaround, which works very well, is to move my scipy part of the script to its own script and then use os.system() to call it with the appropriate arguments. Thanks

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Julian Taylor
On 29.01.2014 20:44, Nathaniel Smith wrote: > On Wed, Jan 29, 2014 at 7:39 PM, Joseph McGlinchy wrote: >> Upon further investigation, I do believe it is within the scipy code where >> there is a leak. I commented out my call to processBinaryImage(), which is >> all scipy code calls, and my memory

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Nathaniel Smith
On Wed, Jan 29, 2014 at 7:39 PM, Joseph McGlinchy wrote: > Upon further investigation, I do believe it is within the scipy code where > there is a leak. I commented out my call to processBinaryImage(), which is > all scipy code calls, and my memory usage remains flat with approximately a > 1MB var

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Joseph McGlinchy
Upon further investigation, I do believe it is within the scipy code where there is a leak. I commented out my call to processBinaryImage(), which is all scipy code calls, and my memory usage remains flat with approximately a 1MB variation. Any ideas? Right now I am getting around it by checking

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Joseph McGlinchy
Perhaps it is an ESRI/Arcpy issue then. I don't see anything that could be doing that, though, as it is very minimal. From: numpy-discussion-boun...@scipy.org [mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Benjamin Root Sent: Wednesday, January 29, 2014 11:10 AM To: Discussion of Numer

Re: [Numpy-discussion] Memory leak in numpy?

2014-01-29 Thread Benjamin Root
Hmmm, I see no reason why that would eat up memory. I just tried it out on my own system (numpy 1.6.1, CentOS 6, python 2.7.1), and had no issues, Memory usage stayed flat for the 10 seconds it took to go through the loop. Note, I am not using ATLAS or BLAS, so maybe the issue lies there? (i don'

Re: [Numpy-discussion] scipy image processing memory leak in python 2.7?

2014-01-29 Thread Joseph McGlinchy
I have updated to scipy 0.13.2 (specifically scipy-0.13.2-win32-superpack-python2.7.exe (59.1 MB)) at http://sourceforge.net/projects/scipy/files/ I am still seeing the memory leak, and it appears to be a little larger (2

Re: [Numpy-discussion] scipy image processing memory leak in python 2.7?

2014-01-29 Thread Ralf Gommers
On Tue, Jan 28, 2014 at 8:08 PM, Joseph McGlinchy wrote: > >>> scipy.version.version > '0.11.0b1' > > >>> numpy.version.version > '1.6.1' > > Is that, or any other, memory leaks present in these versions? > That memory leak isn't, it's only present in 0.13.0-0.13.2. I'm not aware of any other lea