← Back to team overview

dx-packages team mailing list archive

[Bug 1203607] Re: signals connected in panel-service.c:on_entry_added never disconnected

 

** Changed in: unity/5.0
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1203607

Title:
  signals connected in panel-service.c:on_entry_added never disconnected

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  I have observed unity-panel-service on Ubuntu 12.04 consuming hundreds
  of MB of memory (RSS) after about a month of uptime.  I ran ubuntu-
  panel-service 5.20.0 with G_SLICE=always-malloc using Valgrind with
  --leak-check=full --track-origins=yes --show-reachable=yes --num-
  callers=100 for a few hours and attached a leak report.  Here is a
  suspect trace:

  ==25653== 155,736 bytes in 2,163 blocks are possibly lost in loss record 12,412 of 12,412
  ==25653==    at 0x4C2A964: calloc (vg_replace_malloc.c:593)
  ==25653==    by 0x68D8AE0: g_malloc0 (gmem.c:189)
  ==25653==    by 0x60E7B18: g_closure_new_simple (gclosure.c:206)
  ==25653==    by 0x60E907F: g_cclosure_new (gclosure.c:917)
  ==25653==    by 0x61000CD: g_signal_connect_data (gsignal.c:2443)
  ==25653==    by 0x40AC57: on_entry_added (panel-service.c:841)
  ==25653==    by 0x60E8CA1: g_closure_invoke (gclosure.c:777)
  ==25653==    by 0x60F9D70: signal_emit_unlocked_R (gsignal.c:3547)
  ==25653==    by 0x6102098: g_signal_emit_valist (gsignal.c:3296)
  ==25653==    by 0x6102241: g_signal_emit (gsignal.c:3352)
  ==25653==    by 0x4E39734: indicator_object_set_visible (in /usr/lib/libindicator3.so.7.0.0)
  ==25653==    by 0x15F2A844: ???
  ==25653==    by 0x60E8CA1: g_closure_invoke (gclosure.c:777)
  ==25653==    by 0x60F9D70: signal_emit_unlocked_R (gsignal.c:3547)
  ==25653==    by 0x6102098: g_signal_emit_valist (gsignal.c:3296)
  ==25653==    by 0x6102241: g_signal_emit (gsignal.c:3352)
  ==25653==    by 0xA0A5DF6: ??? (in /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2.2.2)
  ==25653==    by 0x60E8CA1: g_closure_invoke (gclosure.c:777)
  ==25653==    by 0x60F9D70: signal_emit_unlocked_R (gsignal.c:3547)
  ==25653==    by 0x6102098: g_signal_emit_valist (gsignal.c:3296)
  ==25653==    by 0x6102241: g_signal_emit (gsignal.c:3352)
  ==25653==    by 0xA0A62FD: ??? (in /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2.2.2)
  ==25653==    by 0xA2C9AC5: dbus_connection_dispatch (in /lib/x86_64-linux-gnu/libdbus-1.so.3.5.8)
  ==25653==    by 0xA09F434: ??? (in /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2.2.2)
  ==25653==    by 0x68D2D52: g_main_context_dispatch (gmain.c:2539)
  ==25653==    by 0x68D309F: g_main_context_iterate.isra.23 (gmain.c:3146)
  ==25653==    by 0x68D3499: g_main_loop_run (gmain.c:3340)
  ==25653==    by 0x51BC42C: gtk_main (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.400.2)
  ==25653==    by 0x407EC1: main (panel-main.c:431)

  I will submit a review request which addresses this.  Note that there
  are other suspicious activity in the log outside the scope of this
  issue.

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