[NumPy-Tickets] [NumPy] #2129: Segfault on umath.cpython-32mu.so

NumPy Trac numpy-tickets@scipy....
Tue May 15 04:32:27 CDT 2012


#2129: Segfault on umath.cpython-32mu.so
------------------------+---------------------------------------------------
 Reporter:  Sachiel     |       Owner:  somebody  
     Type:  defect      |      Status:  needs_info
 Priority:  normal      |   Milestone:  1.7.0     
Component:  numpy.core  |     Version:  devel     
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by Sachiel):

 Just loading and plotting data for 6 RGB images instead of 15, doesn't
 provoke the segfault.

 I've also discovered that if I delete each array after plotting it but
 before rendering on the screen (so, after plt.imshow() but before
 plt.show()), it works OK. So, definitely, it's about and excessive usage
 of memory.

 About your question if it happens immediately, well, the program takes
 it's time to read the data from the HD, and then it becomes slow as it
 start using swap. At one point an empty  (all grey) figure window appears,
 and then the Segmentation Fault message on the console.

-- 
Ticket URL: <http://projects.scipy.org/numpy/ticket/2129#comment:10>
NumPy <http://projects.scipy.org/numpy>
My example project


More information about the NumPy-Tickets mailing list