Well this already looks suspicious:
https://bazaar.launchpad.net/~indicator-applet-developers/notify-
osd/trunk/view/505/src/stack.c#L813
#define FORCED_SHUTDOWN_THRESHOLD 500
....
// FIXME: this is a temporary work-around, I do not like at all, until
// the heavy memory leakage of notify-osd is fully fixed...
// after a threshold-value is reached, "arm" a forceful shutdown of
// notify-osd (still allowing notifications in the queue, and coming in,
// to be displayed), in order to get the leaked memory freed again, any
// new notifications, coming in after the shutdown, will instruct the
// session to restart notify-osd
if (bubble_get_id (bubble) == FORCED_SHUTDOWN_THRESHOLD)
g_timeout_add (defaults_get_on_screen_timeout (self->defaults),
_arm_forced_quit,
(gpointer) self);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725435
Title:
notify-osd a memory hog (memory leak?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/725435/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
