[NumPy-Tickets] [NumPy] #1513: flushing memmap incomplete

NumPy Trac numpy-tickets@scipy....
Thu Jun 17 08:39:42 CDT 2010

#1513: flushing memmap incomplete
 Reporter:  rgommers      |       Owner:  somebody
     Type:  defect        |      Status:  new     
 Priority:  normal        |   Milestone:  2.0.0   
Component:  numpy.core    |     Version:          
 Keywords:  memmap, mmap  |  
 Reported by Geoffrey Irving on the mailing list:

 If I create an mmap'ed array, and then generate another array
 referencing only its base, destruction of the original mmap'ed array
 closes the mmap.  The second array is then prone to segfaults.

 I think the best fix is to put the responsibility for flushing the
 mmap onto the actual mmap object (and therefore the base object)
 directly, so that the numpy memmap object has no cleanup
 responsibilities.  A patch to core/memmap.py follows.  It would be
 nicer to put the mmap_flush class declaration somewhere outside the
 function, but that conflicts with the local "import mmap."

Ticket URL: <http://projects.scipy.org/numpy/ticket/1513>
NumPy <http://projects.scipy.org/numpy>
My example project

More information about the NumPy-Tickets mailing list