kernel-packages team mailing list archive

[James Hunt <1235649@xxxxxxxxxxxxxxxxxx>]

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 %MEM    TIME+  COMMAND
15329 james     20   0 2463m 2,0g  12m R 100,0 26,1   6:51.59 memcheck-x86-li

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_memcheck-x86-linux.so)
==15329==    by 0x408E778: dbus_realloc (dbus-memory.c:678)
==15329==    by 0x408F08C: reallocate_for_length (dbus-string.c:349)
==15329==    by 0x408F12B: set_length (dbus-string.c:390)
==15329==    by 0x408F1A9: open_gap (dbus-string.c:411)
==15329==    by 0x408FA67: copy (dbus-string.c:1198)
==15329==    by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368)
==15329==    by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726)
==15329==    by 0x408DD95: marshal_string (dbus-marshal-basic.c:758)
==15329==    by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840)
==15329==    by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601)
==15329==    by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323)
==15329==
==15329== LEAK SUMMARY:
==15329==    definitely lost: 28 bytes in 1 blocks
==15329==    indirectly lost: 24 bytes in 1 blocks
==15329==      possibly lost: 133,265 bytes in 315 blocks
==15329==    still reachable: 1,154,753,166 bytes in 18,194 blocks
==15329==         suppressed: 0 bytes in 0 blocks



** Attachment added: "vg-20131015.log.gz"
   https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878397/+files/vg-20131015.log.gz

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  New
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions