[Numpy-tickets] [NumPy] #551: numpy.ndarray messed up after unpickling

NumPy numpy-tickets@scipy....
Mon Feb 25 14:12:38 CST 2008

#551: numpy.ndarray messed up after unpickling
 Reporter:  cotackst                   |        Owner:  somebody
     Type:  defect                     |       Status:  new     
 Priority:  normal                     |    Milestone:  1.0.5   
Component:  numpy.core                 |      Version:  1.0.1   
 Severity:  normal                     |   Resolution:          
 Keywords:  pickle, ndarray, segfault  |  
Comment (by rkern):

 Replying to [comment:14 oliphant]:
 > The only real difference is that the memory for the array on unpickling
 is allocated originally as a Python String (because that is what
 unpickling does).  !NumPy uses that memory directly instead of copying it
 to another memory area.

 Do we keep a reference to that string object? If not, what happens to the
 memory when the string's refcount hits 0?

Ticket URL: <http://scipy.org/scipy/numpy/ticket/551#comment:15>
NumPy <http://projects.scipy.org/scipy/numpy>
The fundamental package needed for scientific computing with Python.

More information about the Numpy-tickets mailing list