| Summary: | Please backport memleak patch for dev-util/glade-3.12 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://git.gnome.org/browse/glade/commit/?id=5b131bb14180ce21632534c13a1b88ea28866475 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Justin Lecher (RETIRED)
2012-05-18 13:32:36 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? 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. |