This is a memory leak in pygobject. Lots leaks were fixed in
get_property() last release [1] but set_property() still needs work [2].
-Simon
[1] https://bugzilla.gnome.org/show_bug.cgi?id=726999#c7
[2] https://bugzilla.gnome.org/show_bug.cgi?id=735018
Thank you!
___
On Fri, Jan 2, 2015 at 1:29 PM, Colin Myers wrote:
> Yes, the memory increase is in proportion with the size of the text.
>
>
>
> But it is more likely to be an error in my understanding than a pygobject or
> gtk bug – this is usually the case…
This is a memory leak in pygobject. Lots leaks were
Yes, the memory increase is in proportion with the size of the text.
But it is more likely to be an error in my understanding than a pygobject or
gtk bug – this is usually the case…
Regards,
Colin
From: Gergely Polonkai [mailto:gerg...@polonkai.eu]
Sent: 02 January 2015 08:18
To: Colin Mye
My first thought is that Perl and Glib::Object::Introspection is just fine.
If I were you, I would further debug my own application, with something
like refdbg (http://refdbg.sourceforge.net/ despite the looks, it still
works nowadays) or GObject-list (https://github.com/danni/gobject-list
haven’t
Hi,
After help on this list, I got my API documentation to work properly,
and have since added GObject-Introspection annotations so that I could
use it from perl.
When running the following script:
---
use Glib::Object::Introspection;
Glib::Object::Introspection->setup(
basename => "Joy
Hello,
How big is the memory increase? set_text() allocates memory for text, which
might be the cause.
Best,
Gergely
On 1 Jan 2015 22:55, "Colin Myers" wrote:
> Hello list,
>
> I've been wrangling with a leak in my Pygobject/Gtk application and
> believe the following lines of python demonstrat
