RE : [matplotlib-devel] RE : [Matplotlib-users] crash on matplotlib.matlab import on win32

[Gregory L. <gre...@ff...>]

CXX is the python wrapper generator code used to write most of the C++
python extensions that matplotlib uses.  Among other things, it helps
automate reference counting for python objects, but in many cases needs
some assistance from the operator (me).  Since I've been actively
working on the reference counts in a number of parts of the code to fix
some memory leaks, there is a good chance that I screwed up somewhere.


Thanks for this explanation, it could thus be related to a hard to
reproduce bug (why hard to reproduce? see below)

There are two things that would be useful to know:

  * Is this specific to python 2.3.4?  Is this the same version of
    python on all the machines you tested, or is there a difference
    between the python versions on the machines that crashed and the
    machine that worked?  I also tested on Windows XP with no
    problems, using the enthought edition of python.

It looks more like it is specific to my laptop, cause installing exactly
the same python, numarray and matplotlib on another winXP laptop did not
showed the behavior. It will thus be a hard to reproduce bug, cause I
find only one computer exhibiting this behavior for now (on the other
hand, the behavior of this computer is very reliable: systematic crash
all the time, even after python/nuamrray/matplotlib reinstall ). 
If I try to install another version of python on this laptop (python
2.3.3), it crashes the same...I could try older versions (2.2.3 for
example), but 2.3.X is required for numarray 0.9 so I should go to older
version there also, I prefer to do it only if you find it usefull...

  * If instead of importing TkAgg, you simply import Agg, on a machine
    that crashes, do you still get the crash?  It would be nice to
    narrow the focus.

Yes, exactly the same crash, and with PS backend also...so it does not
seems related to the backend...

I have done a fair amount of work since 0.54.2 fixing more memory leaks
- there is always a possibility that the problem has already been fixed.
If you can provide the information above, I can send you a debug build
of the current development snapshot that might provide more information.
Basically, it prints each function call to stdout which sometimes help
debug a segfault and other errors.

Yes, if you have this for windows I would be happy to test!


It's me that thanks you for your help!

Best regards,

Greg.