Merge lp:~ted/libindicator/lp719457 into lp:libindicator/0.5
Proposed by
Ted Gould
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Charles Kerr | ||||
Approved revision: | 456 | ||||
Merge reported by: | Charles Kerr | ||||
Merged at revision: | not available | ||||
Proposed branch: | lp:~ted/libindicator/lp719457 | ||||
Merge into: | lp:libindicator/0.5 | ||||
Diff against target: |
14 lines (+3/-1) 1 file modified
libindicator/indicator-service.c (+3/-1) |
||||
To merge this branch: | bzr merge lp:~ted/libindicator/lp719457 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Charles Kerr (community) | Approve | ||
Review via email: mp+95619@code.launchpad.net |
Description of the change
Saving the string before doing the remove so the string being free'd doesn't effect us.
To post a comment you must log in.
libindicator doesn't appear to be violating the glib API -- this smells like a bug in GHashTable that we'd be better off reporting upstream instead of using a local band-aid.
Also, nobody's reported this since March 16 last year, and glib has revved several times since then. Maybe it would make sense to CC desrt to see if that valgrind log looks familiar?