Thanks for the report. I think what you are seeing was fixed with the
following commit:
https://git.gnome.org/browse/pygobject/commit/?id=bbfcebdfdc5
On Thu, Dec 18, 2014 at 9:13 AM, Barry Scott wrote:
> This patch seems to fix the cairo_t leak.
>
> --- pygobject-3.10.2/gi/pygi-foreign-cairo.c~
This patch seems to fix the cairo_t leak.
--- pygobject-3.10.2/gi/pygi-foreign-cairo.c~ 2014-12-18 16:56:02.351351606
+
+++ pygobject-3.10.2/gi/pygi-foreign-cairo.c2014-12-18 16:56:02.351351606
+
@@ -60,8 +60,6 @@
{
cairo_t *context = (cairo_t*) data;
-cairo_reference (
On Thu 18 Dec 2014 15:15:10 Barry Scott wrote:
> I am trying to track down a problem with leaking cairo_t context structs
> when using cairo from python. I running under an up to date fedora 20
> system. (I suspect that other structs are leaking as well, but I have not
> deep dived them yet).
>
>
I am trying to track down a problem with leaking cairo_t context structs
when using cairo from python. I running under an up to date fedora 20 system.
(I suspect that other structs are leaking as well, but I have not deep dived
them yet).
The attached example program can be run under valgrind to s
