same problem.
Linux 3.14.0-generic
ubuntu 14.04
kdm
init --user use 1.8GB memory in 9 days
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in ses
** Changed in: unity (Ubuntu Saucy)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to cons
** Changed in: upstart
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
ma
** Changed in: upstart
Status: Fix Committed => Fix Released
** Changed in: upstart
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
ueve
** Changed in: unity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive amoun
** Also affects: landing-plan
Importance: Undecided
Status: New
** Changed in: landing-plan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
** Branch linked: lp:~jamesodhunt/ubuntu/trusty/dbus/bug-1252317
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
m
This bug was fixed in the package upstart - 1.11-0ubuntu1
---
upstart (1.11-0ubuntu1) trusty; urgency=low
[ Dmitrijs Ledkovs ]
* Run as much test-suites as possible, before exiting with failure.
[ James Hunt ]
* New upstream release.
- the global environment is now serial
** Branch linked: lp:~jamesodhunt/ubuntu/trusty/upstart/1.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massi
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu Saucy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
ueve
** Branch linked: lp:~jamesodhunt/upstart/bug-1235649
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive amou
** Tags added: needs-ap-test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive amounts of memory on Ubuntu T
** Branch linked: lp:~jamesodhunt/upstart/bugs-1235649+1203595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
mas
** Changed in: upstart (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: upstart (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
We already have bug 1203595 for having the Session Init connect to the
D-Bus session bus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in sessi
After discussing this with Ted, I think the right answer architecturally
is to move these clients to talking to the session bus, where filtering
of messages will be done for us automatically, and have the session init
register on the session bus, rather than deploying an unreliable change
like havi
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive amounts of memory on Ubuntu Touch
To
TBC, using the patch on #69 results in no memory bloat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive am
FWICS D-Bus is behaving as designed: since the client has not called
dbus_connection_set_wakeup_main_function(), and since D-Bus messaging is
reliable, all libdbus is able to do when a signal is sent to a
connection is cache any messages the client has not yet processed in the
hope that at some fut
Valgrind log from test_nih_dbus_server.c run using 'valgrind --num-
callers=100 ...'.
** Attachment added: "vg-test_nih_dbus_server.log.gz"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878682/+files/vg-test_nih_dbus_server.log.gz
--
You received this bug notifica
On Tue, Oct 15, 2013 at 08:19:53AM -, James Hunt wrote:
> Once again, the biggest offender by a huge margin is dbus:
> ==15329== 1,153,679,208 bytes in 12,025 blocks are still reachable in loss
> record 208 of 208
> ==15329==at 0x402BB88: realloc (in
> /usr/lib/valgrind/vgpreload_memchec
I can now recreate the memory bloat using a basic NIH D-Bus server
program and associated client program.
1) Run the server as:
$ ./test_nih_dbus_server unix:abstract=/com/hunt/james/foo
com.hunt.james.Foo /com/hunt/james/Foo
2) Run the client as:
$ ./test_nih_dbus_client unix:a
** Attachment added: "test_nih_dbus_client.c"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878664/+files/test_nih_dbus_client.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "spam_dbus_server.sh"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878665/+files/spam_dbus_server.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Branch linked: lp:~xnox/ubuntu/saucy/systemd/udevd-ignore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massi
** Changed in: systemd (Ubuntu Saucy)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to
systemd task assigned to me:
- make it possible for systemd-udevd to ignore kernel events from devices
tagged "ignore", using a kernel netlink filter to completely avoid wakeups of
systemd-udevd.
** Changed in: systemd (Ubuntu Saucy)
Status: New => In Progress
** Changed in: systemd (Ub
Another valgrind log taken using the same precedure as above. However,
this time I waited until the init process was consuming over 2GB of RAM.
Top showed:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
15329 james 20 0 2463m 2,0g 12m R 100,0 26,1 6:51.59 memcheck-
Hi Steve,
The trace in #59 was produced by:
- Running Upstart via valgrind which upstart linked against debug builds of nih
and dbus.
- Running a single instance of the test program (#51).
- Running spam.sh (#52).
- Waiting until init was consuming ~200MB, then sending SIGTERM to the
init/valgr
James, how was this valgrind trace produced? The stacktrace doesn't
show anything above the low-level calls in dbus, making it difficult to
pinpoint the actual source of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Just got a much more interesting valgrind run. Juicy excerpt:
==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187
of 188
==9366==at 0x402B965: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==9366==by 0x408E730: dbus_malloc0 (dbus-memory.c:572)
==
So the reason the memory usage wasn't growing after re-exec was because
unity8 didn't automatically reconnect when the dbus connection dropped.
If I kill and restart unity8, the problem reappears.
So the memory usage is indeed associated with the dbus client, even
though disconnecting the client d
I've tested on a mako device here, and the memory usage is not all due
to a misbehaved client. I've tracked down all the clients of the
session init; unity8 is the only long-lived client other than the
bridges, and if I kill unity8 and let it respawn, upstart gains back
some of the memory, but *no
I've also checked this memory usage with valgrind; valgrind doesn't
think there's a leak, at the end of a valgrind session there are only
211,206 bytes "possibly lost" - nowhere near the many MB that we're
seeing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Neither does calling the following help:
dbus_connection_flush (connection);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upsta
Note that the following call on the server side does not resolve the
issue:
while (dbus_connection_dispatch (connection) == DBUS_DISPATCH_DATA_REMAINS)
;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
38 matches
Mail list logo
