Charles Moad wrote:
>> I can't seem to crash TkAgg, but WXAgg and GTKAgg still do.
>> This seems to not be related to the repr issue from before.
>> This is all mpl-cvs btw.
> OK, I'm afraid this one may require John's help to
> debug. I don't know the mpl internals nearly well
> enough to even begin to guess where this could be coming
> The fact that it's a segfault and not an uncaught
> exception means the bug is triggered inside C code.
> <TAB> triggers dir() and getattr() calls, which have to
> traverse the object's internal dictionary. If the
> object is implemented in C/C++, that traversal can do
> arbitrary things, including any number of
> segfault-inducing manipulations.
The canvas object (eg FigureCanvasGTKAgg) is implemented in python.
It inherits from a gtk base class and an Agg base class. It would be
useful to test whether you get this behavior on the GTK and WX
backends (no Agg). My guess is that this is some is caused by a
threading problem, but can't be sure. This would explain why you see
it with GTKAgg and WXAgg but not TkAgg.