After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749651 - Accessing a Gdk.RGBA-member of Gtk.TextTag leaks memory
Accessing a Gdk.RGBA-member of Gtk.TextTag leaks memory
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: Bindings: GTK+ GStreamer WebKitGTK+
0.28.x
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-20 17:38 UTC by gilzad
Modified: 2018-05-22 15:23 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Vala code that reproduces a memleak when accessing a TextTag's RGBA-member. (2.08 KB, text/x-vala)
2015-05-20 17:38 UTC, gilzad 		Details

Description gilzad 2015-05-20 17:38:53 UTC 
Created attachment 303691 [details]
Vala code that reproduces a memleak when accessing a TextTag's RGBA-member.

Hi all,

according to the discussion on the mailing list [1] Vala doesn't free allocated memory after reading from an rgba-member of Gtk.Texttag. More specifically:

After

g_object_get (_tmp26_, "foreground-rgba", &_tmp27_, NULL);

_tmp27_ will never be freed.


The attached example (gdk_rgba.vala) reads from a TextTag's foreground_rgba in a loop for 20 seconds, during which the memory consumption constantly raises.
The line

stdout.printf(tag.foreground_rgba.to_string()+"\n");

is where the leak occours.


Valgrind's dump for that case is uploaded here https://gist.github.com/anonymous/f1aead08848226949f48 .


Let me know if I can do anything.

Thanks & best

gilzad


[1] http://thread.gmane.org/gmane.comp.programming.vala/11446
Comment 1 GNOME Infrastructure Team 2018-05-22 15:23:48 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/500.