Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 416497 - Please backport memleak patch for dev-util/glade-3.12
Summary: Please backport memleak patch for dev-util/glade-3.12
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux Gnome Desktop Team
URL: http://git.gnome.org/browse/glade/com...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-18 13:32 UTC by Justin Lecher (RETIRED)
Modified: 2012-06-16 12:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Lecher (RETIRED) gentoo-dev 2012-05-18 13:32:36 UTC
Please backport this commit
http://git.gnome.org/browse/glade/commit/?id=5b131bb14180ce21632534c13a1b88ea28866475
I was able to hit the memleak a couple of times, which really sucked.
Comment 1 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-05-18 23:34:19 UTC
(In reply to comment #0)
> Please backport this commit
> http://git.gnome.org/browse/glade/commit/
> ?id=5b131bb14180ce21632534c13a1b88ea28866475
> I was able to hit the memleak a couple of times, which really sucked.

As far as I can tell, the part of that patch which contains a memory leak fix was already backported and applied in glade-3.12.1: http://git.gnome.org/browse/glade/commit/?h=glade-3-12&id=5ac8115fd0b47b39cb7d0f52541bf68a437d8b95

How did you determine what piece of code was responsible for the memory leak you were experiencing?
Comment 2 Justin Lecher (RETIRED) gentoo-dev 2012-05-19 06:55:44 UTC
Actually I was guessing that it is glade. I experienced a mem leak a couple of times and I was always working with glade. Specially I think it happens when configuring the liststore columns. But to be honest I am not sure that it is really glade. I just went out and found a mem leak bug somewhere pointing to that bit of code and I hopped to have found a solution. Actually since switching to 13.0 it didn't happen again. But I am not sure if I simply didn't hit that bit of code.
So probably we should close it with invalid.