notification-daemon memory leak

Bug #329564 reported by Antonio Litterio
2
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: notification-daemon

I noticed memory leak in notification-daemon
For reproduced this bug:
-) Open System Monitor for view memory occupation.
-) Open Notification-Settings, select for example standard theme (equal with ubuntu theme)
-) Press button preview with enter button (for open many time popup)
-) Look the memory increase

someone confirm this (with 32bit architecture)?

Additional informations:
notification-daemon-0.4.0-0ubuntu2
Ubuntu Jauntry i686
Gnome 2.25.90

Probably only with i686 the bug is present, because with amd64 work fine...

description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in notification-daemon:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Antonio Litterio (antonio-litterio-gmail) wrote :

I analyzed the source code and I found the problem in file theme.c (equal for both standard and ubuntu theme). It was in incorrectly deallocation of SexyUrlLabel.
With valgrind I noticed the presence of a lot of memory "still reachable".
I think that probably it is libsexy problem, because if I write this simple code:

GtkWidget *tmp = sexy_url_label_new();
gtk_widget_destroy(tmp);

or use
g_object_unref(G_OBJECT(tmp));

the GtkWidget "tmp" created with sexy_url_label_new() it is improperly deallocated.

Changed in notification-daemon:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.