Re: [Matplotlib-users] matplotlib.backends.backend_gtk3cairo memory leak

[Jens N. <jen...@gm...>]

IGtk3Agg should work in you use cairocffi instead of py(2/3)cairo. AFAIK
py(2/3)cairo is more or less unmaintained these days and that function has
never been implemented in a released version.

Best
Jens

tir. 26. maj 2015 kl. 16.27 skrev David <dh...@ra...>:

> >  I take it that it doesn't happen using the GTK3Agg backend?
> GTK3Agg is unimplemented at the GTK3-end:
>
>   File
> "c:\Python34\lib\site-packages\matplotlib\backends\backend_gtk3agg.py",
> line
> 69, in on_draw_event
>     buf, cairo.FORMAT_ARGB32, width, height)
> NotImplementedError: Surface.create_for_data: Not Implemented yet.
>
> > What about the threading portion? Does it happen if you take the
> threading
> > out?
> I removed all calls to threads and swapped Gdk.threads_add_timeout to
> Glib.timeout_add. This made little difference.
>
> However if I comment the call to self.canvas.draw(), the python memory
> utilisation sits at 30.8Mb (but the graph does not update of course).
>
> Thanks
>
> David
>
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/matplotlib-backends-backend-gtk3cairo-memory-leak-tp45614p45616.html
> Sent from the matplotlib - users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>