Copied to hardy-updates.
** Changed in: notification-daemon (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I've reproduced the bug in the version of notification-daemon included
in the Hardy 8.04 release, and have verified that the package in Hardy-
proposed definitely improves the memory usage of it -- doing (in bash):
$ for ((i = 1; i = 1000; i++)) ; do notify-send -i
Oops, my bad. :( Thanks for fixing.
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to notification-daemon in ubuntu.
--
desktop-bugs mailing list
I did another hardy-proposed upload that fixes another leak, the numbers
should be even better now.
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Accepted into -proposed, please test and give feedback here
** Changed in: notification-daemon (Ubuntu Hardy)
Status: Confirmed = Fix Committed
** Tags added: verification-needed
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug
Ok, the update in proposed seems to behave much better. I enabled -proposed as
described here:
https://wiki.ubuntu.com/Testing/EnableProposed
Using the prior version, 0.3.7-1ubuntu11, I repeated the steps described in the
initial bug description.
total32164K
...
total57896K
After
** Changed in: notification-daemon (Ubuntu)
Status: New = In Progress
Target: None = ubuntu-8.04.1
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
notification-daemon (0.3.7-1ubuntu12) intrepid; urgency=low
.
* debian/patches/01_ubuntu_theme.patch:
- Fixed memory leak reported in lp: #67129
- Testing has shown significant improvement but there are
inconclusive indicators that another much smaller leak may exist.
*
** Description changed:
: jm 325...; ps auxww | grep 6276
jm6276 0.0 1.0 237004 10976 ?SOct14 0:47
/usr/lib/notification-daemon/notification-daemon
yep, 237004 KB. looks like a leak.
The process is still running; let me know if you want maps files, etc.
+
+
** Changed in: notification-daemon (Ubuntu Hardy)
Importance: Undecided = Medium
Status: New = Confirmed
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug was fixed in the package notification-daemon - 0.3.7-1ubuntu12
---
notification-daemon (0.3.7-1ubuntu12) intrepid; urgency=low
* debian/patches/01_ubuntu_theme.patch:
- Fixed memory leak reported in lp: #67129
- Testing has shown significant improvement but there
** Description changed:
: jm 325...; ps auxww | grep 6276
jm6276 0.0 1.0 237004 10976 ?SOct14 0:47
/usr/lib/notification-daemon/notification-daemon
yep, 237004 KB. looks like a leak.
The process is still running; let me know if you want maps files, etc.
I have the same problem running under Xubuntu (ie. xfce4). I'll show you
tomorrow Sebastien.
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The new log is better, the --num-callers= used seems limited though,
using a higher value would be nice, the ubuntulooks debug symbols seems
to not be installed either, could you get a new log after changing
those?
--
notification-daemon using 237MB of memory
Seeing this also in Hardy, notification-daemon 0.3.7-1ubuntu11.
** Attachment added: valgrind.log
http://launchpadlibrarian.net/13462313/valgrind.log
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member
the valgrind log lists some leaks but since the corresponding debug
packages are not install it lacks the detailed required to work on the
issue
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of
I was recently able to reproduce the symptom from the comment I posted
on 2007-07-27 using n-d trunk, so I don't believe it's fixed
upstream. Using valgrind I tried to identify the leak but was unable.
Anything I can do to help further?
On Tue, Apr 15, 2008 at 9:27 AM, Sebastien Bacher [EMAIL
valgrind log when liferea and rhythmbox both are shooting new
notification bubbles for about 10minutes. I installed most of the
-dbgsym packages required for more detailed log.
** Attachment added: leak2.txt
http://launchpadlibrarian.net/13463953/leak2.txt
--
notification-daemon using 237MB
Having upgraded to Gutsy I can verify this bug is still preset. Any
ideas? I'd be willing to look into this further but would probably
need some guidance.
On 9/18/07, Brian Fallik [EMAIL PROTECTED] wrote:
Is there an easy way to test 0.3.7 on Feisty? Download n-d and build
the source?
Is there an easy way to test 0.3.7 on Feisty? Download n-d and build
the source? Backport Gutsy's? Etc?
I can also just wait for Gutsy.
On 9/13/07, Brian Fallik [EMAIL PROTECTED] wrote:
Could be. That's in 0.3.7 (gutsy); eft is at 0.3.6.
On 9/12/07, shacharr [EMAIL PROTECTED] wrote:
Could be. That's in 0.3.7 (gutsy); eft is at 0.3.6.
On 9/12/07, shacharr [EMAIL PROTECTED] wrote:
http://trac.galago-project.org/changeset/2971
Maybe this changeset will help?
The relevant bug report ( http://trac.galago-project.org/ticket/105 )
talks about a memory leak fixed.
--
http://trac.galago-project.org/changeset/2971
Maybe this changeset will help?
The relevant bug report ( http://trac.galago-project.org/ticket/105 )
talks about a memory leak fixed.
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug
I've experienced exactly the same problem. I'd noticed that my computer
was running very sluggishly and it felt like a memory issue. CPU usage
was normal, yet all of X seemed painfully slow.
After inspecting g-s-m I saw notification-applet was using ~60Megs, which
seemed a bit extreme.
Attachments apparently don't come by email. Here's the log for real.
** Attachment added: Valgrind log of n-m
http://librarian.launchpad.net/7701119/notification-daemon.valgrind.tar.gz
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug
I'm seeing the issue too, attaching two valgrind logs, each showing one
notification from banshee. I'm using the default libnotify style.
** Attachment added: valgrind.log.2881
http://librarian.launchpad.net/7642593/valgrind.log.2881
--
notification-daemon using 237MB of memory
** Attachment added: valgrind.log.2947
http://librarian.launchpad.net/7642595/valgrind.log.2947
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
** Changed in: notification-daemon (Ubuntu)
Status: Needs Info = Unconfirmed
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
On 5/13/07, Andrew Conkling [EMAIL PROTECTED] wrote:
In the meantime, it might be worth mentioning some specifics on my system:
thinking of things that use libnotify, I'm running Pidgin with the libnotify
plugin, Rhythmbox with song change notifications on, and the ZeroConf
Service Discovery
the log might be useful, not easy to say without having it available
though
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for notification-daemon in
Getting a valgrind log would be useful to spot an incorrect usage
** Changed in: notification-daemon (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Needs Info
--
notification-daemon using 237MB of memory
https://bugs.launchpad.net/bugs/67129
You received this bug
On 5/13/07, Sebastien Bacher [EMAIL PROTECTED] wrote:
Getting a valgrind log would be useful to spot an incorrect usage
Would this still be useful if the memory usage isn't ridiculously extreme?
Currently n-d is using 22 MB, which still seems extreme than the 1 or 2 MB
it uses when I first
I just noticed this problem for the first time, n-d was using 70 MB. I'm
using the Darkilouche theme. Has anyone determined this to be theme-
specific? What kind of information--valgrind, gdb, etc.--would be useful
to capture?
** Changed in: notification-daemon (Ubuntu)
Status: Rejected =
fwiw, I switched to the Human theme a few months back, and this problem
hasn't reappeared. I suspect it was something to do with the H2O-
gtk2-Amber theme.
--
notification-daemon using 237MB of memory
https://launchpad.net/bugs/67129
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: notification-daemon (Ubuntu)
Status: Needs Info = Rejected
--
Do you get the same problem with another theme too?
** Changed in: notification-daemon (Ubuntu)
Status: Unconfirmed = Needs Info
--
notification-daemon using 237MB of memory
https://launchpad.net/bugs/67129
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I'm on Dapper; so it's 0.3.4-0ubuntu8. I presume you mean what GNOME
theme? it's one of the H2O themes: H2O-gtk2-Amber.
I could restart it with valgrind -- unfortunately it'd be assuming that
this will happen again, and I can't guarantee that :(
--
notification-daemon using 237MB of memory
36 matches
Mail list logo
