Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: dbus (Ubuntu Hardy)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
When I executed dbus-daemon with verbose mode(described in man page),
I could see strange thing after few minutes(output is grepped).
-
6315: Message 0xb7ff7fe8 (4 /org/freedesktop/DBus org.freedesktop.DBus
NameOwnerChanged 'sss') for null added to outgoing queue 0xb7fe7a78, 1 pending
to
yes it definitely still exists, i'm on maverick, and it has been
occuring for the last 2 months. and really hard to produce.. could
anybody help us here? feel free to ask me anything that i should
provide, i would love to, i just don't know what to provide right now.
and it's really hard to
Sorry for bringing this up again, but I see quite similar symptoms on a
current natty install with kernel 2.6.37-5 and dbus 1.4.0-0ubuntu1 on a
DELL E6510 laptop (NVIDIA NVS 3100M). When I try to suspend on battery
(which fails because 2 tasks fail to freeze), dbus starts acting mad
and currently
Your most recent post was discouraging: if the brightest minds of
Canonical aren't immediately clear how to trace the single largest
problem undermining my productive use of Kubuntu, how do I stand a
chance? :-( But I now have a couple of hunches to offer. So far, these
are only hunches, which
Interesting, it's your *session* bus that has the high memory
consumption. That's a bit more tricky to debug, since it's started from
within X.
In fact, I don't have any idea how to do that at the moment :-/
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this
Thank you for the layman's summary. It was a *_very helpful_* summary.
This KDE session loaded 28 hours ago. These are my current stats:
br...@xenophon:~$ ps aux | grep dbus-daemon
102 1201 0.0 0.0 27196 3620 ?Rs Oct14 2:13 dbus-daemon
--system --fork
bruce 8802 2.9
By the time that I went to generate a massif.out report, the KDE
session was up to its neck in swap page quicksand and I forgot the
instruction about killing dbus-daemon first. I eventually did look up
the instructions, and the report is attached. But along the way,
valgrind reported that it had
It is 8.5 hours since I restarted the system and logged back into KDE.
Here is the output of ps -avx:
br...@xenophon:~$ ps avx | grep dbus-daemon
1235 ?Ss 0:20 3 311 23596 1364 0.0 dbus-daemon --system
--fork
1894 ?Ss 0:00 0 311 23016 812 0.0
On Mon, 2009-10-12 at 04:13 +, Bruce Miller wrote:
What has not yet declined is the number of zombie bash processes being
reported by top. These also appear to be related to amarok Are they also
connected to this dbus-daemon issue?
Not sure, but they're definitely amarok's fault.
For
br...@xenophon:~$ valgrind --tool=massif /bin/dbus-daemon --system
==1225== Massif, a heap profiler
==1225== Copyright (C) 2003-2009, and GNU GPL'd, by Nicholas Nethercote
==1225== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright
info
==1225== Command: /bin/dbus-daemon --system
On Mon, 2009-10-12 at 13:18 +, Bruce Miller wrote:
br...@xenophon:~$ valgrind --tool=massif /bin/dbus-daemon --system
==1225== Massif, a heap profiler
==1225== Copyright (C) 2003-2009, and GNU GPL'd, by Nicholas Nethercote
==1225== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for
Here's the new massif.out
** Attachment added: massif.out.14298
http://launchpadlibrarian.net/33495789/massif.out.14298
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Mon, 2009-10-12 at 14:22 +, Bruce Miller wrote:
Here's the new massif.out
** Attachment added: massif.out.14298
http://launchpadlibrarian.net/33495789/massif.out.14298
OOI how long did you leave this running for? You might need to let it
accumulate more data so that the leak is
On Mon, 2009-10-12 at 14:22 +, Bruce Miller wrote:
Here's the new massif.out
** Attachment added: massif.out.14298
http://launchpadlibrarian.net/33495789/massif.out.14298
I do not believe that this shows a memory leak, merely a usual increase
of heap size due to excessive repeated
dbus-daemon appears to be the main cause of the unusable system
performance I am experiencing on my Kubuntu Karmic setup:
br...@xenophon:~$ uname -a
Linux Xenophon 2.6.31-13-generic #44-Ubuntu SMP Sat Oct 10 15:27:14 UTC 2009
x86_64 GNU/Linux
br...@xenophon:~$ lsb_release -a
No LSB modules are
Further to above, I updated the kernel last night. The system has been
up less than 24 hours. To the best of my recall, I have not logged out
of and back into the current KDE session during that time.
br...@xenophon:~$ free
total used free sharedbuffers cached
Further to above, I have killed amarok, and dbus-daemon memory
consumption has declined slightly.
What has not yet declined is the number of zombie bash processes being
reported by top. These also appear to be related to amarok Are they also
connected to this dbus-daemon issue?
br...@xenophon:~$
Sorry to be swamping this thread with messages.
In an effort to isolate problems on my system, I have:
(1) temporarily removed amarok and its two helper packages
(2) restarted the system
top continues to report dozens of zombie bash instances. They are
spawned fast and many (?) appear to be
Hi Bruce,
I'm the original filer of this bug report and also the writer of that
little bit of code that bash is running (perhaps not coincidentally).
It's part of a superkaramba theme I made a while back, so you might
check to see if that's running. Also, if the bash processes aren't being
Indeed; sorry, should have checked more thoroughly when sponsoring, it
looked like this was actually tested. Thanks for catching! I rejected
the upload.
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs,
On Mon, 2009-08-17 at 18:00 +, Steve Langasek wrote:
As far as I'm able to tell, setting --disable-userdb-cache has *no*
effect on the code in the hardy version of dbus; it sets a define in
config.h which is then never used. Martin, can you confirm this, or
else let me know what I've
I've reviewed the package in hardy-proposed and, since the effects of a
configure flag are non-local and non-obvious, took a closer look at what
this option changed.
As far as I'm able to tell, setting --disable-userdb-cache has *no*
effect on the code in the hardy version of dbus; it sets a
On Thu, 2009-08-06 at 22:45 +, near wrote:
As i run an archlinux, it's only a comment to help you find out. i'll
post this to the dbus bugtracker
Again, please run massif over this to track where the memory is going.
It may simply be unreturned heap memory.
Scott
--
Scott James Remnant
Greetings again friends,
I also still have this memory issue happening. However, I have been
able to prevent it by avoiding certain programs. I have found that if I
just run KDE (Kubuntu) and use Kate and Dolphin, then the memory
increase does not happen. But if I use nautilus from KDE, it
There's definitively something, but it appears only after a few weeks of
using gnome. My main use is pidgin (always running) and several
instances of epiphany (opened and closed several instances in a day).
I think the issue is with epiphany (or something close to it) :
* Here is a ps aux | grep
The patch makes sense (I subscribed main sponsors), but it worries me
that it is still perceived in Karmic (which doesn't disable the userdb
cache). Is it confirmed that it is the very same problem?
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug
On Wed, 2009-07-29 at 09:13 +, Martin Pitt wrote:
The patch makes sense (I subscribed main sponsors), but it worries me
that it is still perceived in Karmic (which doesn't disable the userdb
cache). Is it confirmed that it is the very same problem?
I've not seen any evidence of a true
Sponsored. Colin, Steve, can you please process?
** Changed in: dbus (Ubuntu Hardy)
Status: Confirmed = In Progress
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a pretty intrusive change, though, and I wouldn't accept it for
intrepid or jaunty. However, with hardy being LTS it will stay around
for a while, so with thorough testing the risk is manageable with proper
testing IMHO.
I'd like this to stay in -proposed for at least two weeks, and get
Thanks Scott for the clarification. So I close the Karmic task, and any
memory leak still visible in Karmic should get a new bug report.
** Also affects: dbus (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: dbus (Ubuntu)
Status: New = Fix Released
--
About the leak I saw in Karmic, I couldn't reproduce it with valgrind, so no
evidence from my side.
For what it's worth, dbus' ~800MB memory usage was during Nepomuk's initial
index of my ~53000 files. Subsequent indexes and crawls didn't cause dbus to
fill up my RAM. So maybe it was just
I know this bug is supposed to be fixed, but I'm sure I'm seeing it on Karmic.
dbus-daemon is using ~800MB here. Everything matches what is described in this
thread, so I've decided not to open a new bug.
How can I provide additional useful information about this leak?
--
dbus-daemon memory
Khashayar: Run /etc/init.d/dbus stop, then
valgrind --tool=massif /usr/bin/dbus-daemon --system
like I did, it'll create a massif.out file, which you'll need to chown to
messagebus, then kill dbus-daemon and add it as an attachment. Since killing
dbus takes out any application on a bus, you'll
A statement explaining the impact of the bug on users and justification for
backporting the fix to the stable release:
Fixes memory leak
An explanation of how the bug has been addressed in the development
branch, including the relevant version numbers of packages modified in
order to implement
Let's try this again - use this patch.
** Attachment added: re-enable userdb cache to fix memory leak
http://launchpadlibrarian.net/29412863/dbus-disable-disable-userdb-cache.patch
** Changed in: dbus (Ubuntu)
Status: Invalid = New
--
dbus-daemon memory leak
On Wed, 2009-07-22 at 05:46 +, James Andrewartha wrote:
So are you going to fix the memory leak in hardy, or should I open a new
bug asking for an SRU?
If you'd like an SRU, the procedure for doing so is here:
http://wiki.ubuntu.com/StableReleaseUpdates
(note it doesn't require that you
So are you going to fix the memory leak in hardy, or should I open a new
bug asking for an SRU?
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Fri, 2009-07-17 at 02:54 +, Hei Ku wrote:
I tried to kill dbus-daemon, but KWin died on me and it killed my whole
session. How can I do it gracefully?
You can't, I'm afraid.
Scott
--
Scott James Remnant
sc...@canonical.com
--
dbus-daemon memory leak
r...@quoll:~ # date;ps avx|grep dbus
Thu Jul 16 01:04:02 WST 2009
12667 ?Ss 0:00 0 346 102733 50456 0.6 /usr/bin/dbus-daemon
--system
27136 pts/1S+ 0:00 0 101 4166 940 0.0 grep dbus
r...@quoll:~ # date;ps avx|grep dbus
Thu Jul 16 01:14:50 WST 2009
12667 ?
On Thu, 2009-07-16 at 06:43 +, James Andrewartha wrote:
r...@quoll:~ # date;ps avx|grep dbus
Thu Jul 16 01:04:02 WST 2009
12667 ?Ss 0:00 0 346 102733 50456 0.6
/usr/bin/dbus-daemon --system
27136 pts/1S+ 0:00 0 101 4166 940 0.0 grep dbus
OK, I've done this and there's a massif.out, but it's not being added to
even though dbus' memory usage is increasing:
r...@quoll:~ # date;ps xva|grep dbus
Thu Jul 16 22:39:13 WST 2009
14241 pts/1S+ 0:00 0 101 4162 840 0.0 grep dbus
26826 ?Ss 0:01 0 1461
On Thu, 2009-07-16 at 15:07 +, James Andrewartha wrote:
OK, I've done this and there's a massif.out, but it's not being added to
even though dbus' memory usage is increasing:
You need to terminate the dbus process, and then attach the massif.out
file ;-)
status incomplete
Scott
--
Permissions fail:
==26826== error: can't open output file '/root/massif.out.26824'
==26826==... so profiling results will be missing.
I'll try again and set the ownership to messagebus on massif.out this time.
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received
** Attachment added: output from valgrind --tool=massif /usr/bin/dbus-daemon
--system
http://launchpadlibrarian.net/29153450/massif.out.1042
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks, here's that re-printed
** Changed in: dbus (Ubuntu)
Status: Incomplete = Confirmed
** Attachment added: ms_print.1042
http://launchpadlibrarian.net/29154162/ms_print.1042
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification
MB
9.547^ ,,
| ,,@@@#
| ,,,@@#
|
Note that this clearly isn't the original reporter's problem, since the
version he is using is later
** Changed in: dbus (Ubuntu)
Status: Fix Released = Invalid
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member
I tried to kill dbus-daemon, but KWin died on me and it killed my whole
session. How can I do it gracefully?
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
There's no particular proof that this is a memory leak.
Messages have a timeout attached to them, if an application sends
messages in very quick succession, they will build up inside D-Bus while
it waits for the timeout.
If an application continues to send messages, you'll just end up with
more
It renders the machine unusable, and it will even prevent me from
restarting kdm. So, if it is not a memory leak, it behaves like one, and
whether it is a memory leak or not is just semantics. The problem should
be fixed. If it's an excessive load that will render D-Bus unusable,
then you have a
On Wed, 2009-07-15 at 12:27 +, Hei Ku wrote:
It renders the machine unusable, and it will even prevent me from
restarting kdm. So, if it is not a memory leak, it behaves like one, and
whether it is a memory leak or not is just semantics. The problem should
be fixed. If it's an excessive
Don't patronize me, please. I know that D-Bus shouldn't take 2GB of RAM
and fill in all available swap space while sitting idle.
I don't have the same setup as when the bug was reported, but I will try to
reproduce it and send the output of ps avx
Now, have you tried to reproduce it, or are you
On Wed, 2009-07-15 at 13:14 +, Hei Ku wrote:
Don't patronize me, please. I know that D-Bus shouldn't take 2GB of RAM
and fill in all available swap space while sitting idle.
Then prove it is.
Scott
--
Scott James Remnant
sc...@canonical.com
--
dbus-daemon memory leak
I had the same leak and found it was the Oxygen System Monitor, querying
several times per second for Amarok information, even if Amarok is not running.
Removing the system monitor from the desktop stopped the leak for me, at least
for now.
--
dbus-daemon memory leak
Same situation here (Kubuntu Intrepid, dbus-daemon currently at 400M).
Unfortunately the mentioned possible workarounds do nothing for me: I
don't run vino-server or Akregator, I've disabled Akonadi, and I've
stopped using Amarok due to this problem. This is really an unpleasant
situation... I
Had the same ugly thing myself. Most of my KDE apps (akregator, amarok etc)
would cause that dbus-daemon memory leak instantly.
The problem is now gone when I stopped the vino-server. Also, solves the
problem described in that threat
http://www.uluga.ubuntuforums.org/showthread.php?t=1125401 .
Also have this problem in Jaunty. How do I notice? After few days
without logging off my system uses 2GB of memory without any application
running. Right now, dbus-daemon uses 668MB of resident memory. After
relog, my system uses somewhere between 400-800MB with few running
applications. I
After upgrading to jaunty, I also have the dbus-daemon memory. I can
see it increase in size.
I have narrowed it down to using dolphin and kate. I'm not sure if has
anything to do with accessing ssh shares, samba shares, etc, because I
access many drives with dolphin. Also, I have Kubunu
I have now installed the RC of jaunty 9.04.
Installed all the extra programs I use.
The dbus-daemon run away memory leak is still here.
Rebooted and individually loaded the programs that I use and leave running..
After running each one I waited to see if dbus-daemon would start increasing
screenshot of dbus-daemon using 438MG memory.
machine uptime was only 20 hours.
apt-cache policy dbus
dbus:
Installed: 1.2.12-0ubuntu2
Candidate: 1.2.12-0ubuntu2
Version table:
*** 1.2.12-0ubuntu2 0
500 http://gb.archive.ubuntu.com jaunty/main Packages
100
This is happening on Jaunty for me too
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
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
I have the same problem as well.
Running Intrepid with Compiz.
I have not been able to determine which program this dbus problem is related
to. It happened a few times while I was using OpenOffice 3, banshee,
sound-juicer, liferea, firefox, evolution, and others.
dbus-daemon all of a sudden
Not sure if it's related, but I have one hardy server where dbus-daemon
gradually increases its memory usage over time. The only thing using
dbus on the server is avahi-daemon.
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a
If I run kontact, dbus-daemon uses over 2 GB of ram and 100% cpu after a
day. Running dbus-monitor shows a constant stream of activity from
akonadi. If I kill kontact and the various akonadi services, things go
back idle. This is with the latest jaunty, and has been occuring for a
couple of weeks.
Confirmed in Intrepid. After 3 days, dbus-daemon is taking more than
300MB of system memory. Something is wrong with this program.
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
66 matches
Mail list logo
