Re: [Matplotlib-users] Error in atexit._run_exitfuncs

[Benjamin R. <ben...@ou...>]

What it means, specifically, is that one (or more) figure objects still in
memory at the time of exiting the python interpretor are missing the
expected canvas attribute. I see this happen in various backends from time
to time. The best I can figure is that somehow, the destructor for the
figure has already been called (as it should), which should eliminate its
"FigureManager" instance, but for some reason, that figure manager is still
around and its destructor finally tries to destroy the canvas, which is
already gone.

It is really an odd bug, and I am fairly certain my diagnostic isn't quite
right because I never was able to make a SSCE for
testing/debugging/traceback purposes. The closest I was able to get was
with a preliminary version of the animation framework Ryan May and I were
working on a few years back. His code was holding some extra references,
while destroying other objects... it was weird.

Sorry, I don't have any solutions for you. Maybe someone else will.

Ben Root


On Wed, Jun 25, 2014 at 8:29 AM, <kei...@bt...> wrote:

> I am running matplotlib 1.3.1 under Ubuntu 13 and python3.
> Everything works fine, but I get this message every time:
>
>   Error in atexit._run_exitfuncs:
>   AttributeError: 'FigureManagerGTK3Cairo' object has no attribute 'canvas'
>
> What does it mean, and how do I stop it?
>
> Keith
>
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>