Ubuntu
libnotify package

  1. Bug #725435
  2. Comment #4

Comment 4 for bug 725435

Revision history for this message
Glen Luscombe (glenluscombe) wrote :

My sincere apologies Rolf, I hadn't thought of the intricacies of running Valgrind on a daemon.

Does the memory leak occur soon after a reboot/login, or does it take time to accumulate?

I had a go myself at creating a Valgrind on notify-osd, and this is what worked for me:
1. killall notify-osd
2. G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=~/notify-osd-valgrind.log /usr/lib/notify-osd/notify-osd

You should be able to see notifications again once Valgrind has had time to start.

Then perhaps keep it running until you notice a large amount of memory in use, but this may be impractical for you if it takes days/weeks for the 1.2GB to accumulate (notify-osd is never more than 1.5MB in my system - but 106MB with Valgrind). Note as well, it will not show up in top/ps as notify-osd, but as memvheck-i386 or memcheck-amd64 depending on your distro (that might be helpful info too).

Then just kill it in the terminal with a Ctrl+C.