Newer bug like this, still affecting at least Ubuntu 16.04: #725435
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378193
Title:
Memory leak in notify-osd
To manage notifications about this bug go t
** No longer affects: notify-osd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378193
Title:
Memory leak in notify-osd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Anyone wishing to add further, more up to date valgrind reports on this bug
should do so on bug #610389 instead.
This specific issue is considered fixed, but it is expected there may be a few
more in need of fixing.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You receive
** Changed in: notify-osd
Status: New => Fix Released
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
could those still having an issue in lucid open a new bug with a
valgrind log rather than comment on a closed bug?
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Leak also confirmed here on both upgrades and fresh installations (two
laptops and three workstations). Memory climbs with each notification
until I have to reboot because of memory consumption.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notificatio
Leak confirmed here too on a fresh installation of Lucid (less than a
week). Over 300 Mio after 3 days without reboot.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm the memory leak in 10.04 as well, growing to over 1GB of
memory over time, obviously depending how many notifications are
displayed.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which
I am adding libnotify support to a program, and I was using the
following function to set the icon:
notify_notification_set_icon_from_pixbuf
While using the program, notify-osd climbed to over 1GB of memory used.
Everytime the notification was updated, the memory usage grew.
I commented out the
Whatch the duplicate #569909 for full system info.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
ISame problem in ubuntu lucid RC1.
** Changed in: notify-osd
Status: Fix Released => New
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Marking the upstream bug fixed released too.
** Changed in: notify-osd
Importance: Undecided => High
** Changed in: notify-osd
Status: Confirmed => Fix Released
** Changed in: notify-osd
Milestone: None => ubuntu-9.10-beta-freeze
** Changed in: notify-osd
Assignee: (unassigne
** Changed in: notify-osd (Ubuntu Karmic)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
i filed a new bug 405364 for the leak that is left after this.
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug was fixed in the package notify-osd - 0.9.15-0ubuntu2
---
notify-osd (0.9.15-0ubuntu2) karmic; urgency=low
(cherry-pick rev 357 from lp:~asac/notify-osd/lp378193_tile_memleak)
* fix LP: #378193 - huge memory leak in notify-osd; turned out the biggest
share of
memory
i can confirm that the huge tile block mem leak is gone after the patch:
==16630== 1,362,696 (54,552 direct, 1,308,144 indirect) bytes in 39 blocks are
definitely lost in loss record 217 of 218
==16630== at 0x4C25684: calloc (vg_replace_malloc.c:397)
==16630== by 0x74ED187: g_malloc0 (in /usr/lib
fix available in branch attached. merge requested into lp:notify-osd:
https://code.edge.launchpad.net/~asac/notify-
osd/lp378193_tile_memleak/+merge/9326
** Changed in: notify-osd
Status: New => Confirmed
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received thi
** Branch linked: lp:~ubuntu-desktop/notify-osd/ubuntu
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Also affects: notify-osd
Importance: Undecided
Status: New
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
** Branch linked: lp:~asac/notify-osd/lp378193_tile_memleak
--
Memory leak in notify-osd
https://bugs.launchpad.net/bugs/378193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
patch that potentially fixes tile memleaks in bubble.c - which should be
the biggest cake from this huge memleak; also refactor "tile" memory to
make it easier to copy code in future.
** Attachment added: "lp378193_tile.patch"
http://launchpadlibrarian.net/29573141/lp378193_tile.patch
--
Memo
i ran valgrind to get an initial idea. test: search for google in
gwibber, wait for about 12 notifications, get this:
First a few probably obvious leaks (stripped a bit); further down the
full valgrind output.
==16630==
==16630==
==16630== 58,336 (15,360 direct, 42,976 indirect) bytes in 23 blo
this is a release blocker; notify-osd grows to 587m 356m within less
than a day (maybe even 5 hours?):
$ ps auxw | grep notify-osd | grep -v gre
asac 24967 0.9 17.7 602272 365576 ? S12:22 2:52
/usr/lib/notify-osd/notify-osd
$ uptime
17:14:45 up 19:41, 6 users, load average: 0.
I can confirm this. It seems to happen when notify-osd displays icons in
the bubble:
I am using Banshee, which displays notifications with album art on track
changes. One album cover is about 1.7 MB in size. This causes notify-osd
to use about 10 MB more on _each_ track change when listening to th
24 matches
Mail list logo