← Back to team overview

dx-packages team mailing list archive

[Bug 1234673] Re: indicator-messages crashes and entry call is missed for the user

 

phablet@ubuntu-phablet:~$ G_DEBUG=fatal_criticals valgrind /usr/lib/arm-linux-gnueabihf/indicator-messages/indicator-messages-service 
==3132== Memcheck, a memory error detector
==3132== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==3132== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==3132== Command: /usr/lib/arm-linux-gnueabihf/indicator-messages/indicator-messages-service
==3132== 
==3132== Invalid read of size 4
==3132==    at 0x493D0A4: g_object_unref (gobject.c:3089)
==3132==    by 0x499FA6B: g_source_callback_unref (gmain.c:1549)
==3132==    by 0x499FDD3: g_source_destroy_internal (gmain.c:1208)
==3132==    by 0x49A1B9B: g_main_context_dispatch (gmain.c:3089)
==3132==    by 0x49A1DC9: g_main_context_iterate.isra.22 (gmain.c:3712)
==3132==    by 0x49A20E7: g_main_loop_run (gmain.c:3906)
==3132==    by 0xC96F: main (messages-service.c:252)
==3132==  Address 0x4cd9e20 is 0 bytes inside a block of size 52 free'd
==3132==    at 0x482E25C: free (vg_replace_malloc.c:446)
==3132==    by 0x4951E35: g_type_free_instance (gtype.c:1938)
==3132==    by 0x4954ACF: g_value_unset (gvalue.c:274)
==3132==    by 0x1275D: _indicator_messages_service_skeleton_handle_method_call (indicator-messages-service.c:1443)
==3132==    by 0x48E59B7: skeleton_intercept_handle_method_call (gdbusinterfaceskeleton.c:609)
==3132==    by 0x48D4CBB: call_in_idle_cb (gdbusconnection.c:4868)
==3132==    by 0x49A1B69: g_main_context_dispatch (gmain.c:3065)
==3132==    by 0x49A1DC9: g_main_context_iterate.isra.22 (gmain.c:3712)
==3132==    by 0x49A20E7: g_main_loop_run (gmain.c:3906)
==3132==    by 0xC96F: main (messages-service.c:252)
==3132== 
==3132== Invalid read of size 4
==3132==    at 0x49527B4: g_type_check_instance_is_a (gtype.c:3970)
==3132==    by 0x493D0B5: g_object_unref (gobject.c:3089)
==3132==    by 0x499FA6B: g_source_callback_unref (gmain.c:1549)
==3132==    by 0x499FDD3: g_source_destroy_internal (gmain.c:1208)
==3132==    by 0x49A1B9B: g_main_context_dispatch (gmain.c:3089)
==3132==    by 0x49A1DC9: g_main_context_iterate.isra.22 (gmain.c:3712)
==3132==    by 0x49A20E7: g_main_loop_run (gmain.c:3906)
==3132==    by 0xC96F: main (messages-service.c:252)
==3132==  Address 0x4cd9e20 is 0 bytes inside a block of size 52 free'd
==3132==    at 0x482E25C: free (vg_replace_malloc.c:446)
==3132==    by 0x4951E35: g_type_free_instance (gtype.c:1938)
==3132==    by 0x4954ACF: g_value_unset (gvalue.c:274)
==3132==    by 0x1275D: _indicator_messages_service_skeleton_handle_method_call (indicator-messages-service.c:1443)
==3132==    by 0x48E59B7: skeleton_intercept_handle_method_call (gdbusinterfaceskeleton.c:609)
==3132==    by 0x48D4CBB: call_in_idle_cb (gdbusconnection.c:4868)
==3132==    by 0x49A1B69: g_main_context_dispatch (gmain.c:3065)
==3132==    by 0x49A1DC9: g_main_context_iterate.isra.22 (gmain.c:3712)
==3132==    by 0x49A20E7: g_main_loop_run (gmain.c:3906)
==3132==    by 0xC96F: main (messages-service.c:252)
==3132== 

(process:3132): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
==3132== 
==3132== HEAP SUMMARY:
==3132==     in use at exit: 154,313 bytes in 3,612 blocks
==3132==   total heap usage: 13,086 allocs, 9,474 frees, 450,747 bytes allocated
==3132== 
==3132== LEAK SUMMARY:
==3132==    definitely lost: 131 bytes in 3 blocks
==3132==    indirectly lost: 61 bytes in 1 blocks
==3132==      possibly lost: 9,376 bytes in 296 blocks
==3132==    still reachable: 135,833 bytes in 3,199 blocks
==3132==         suppressed: 0 bytes in 0 blocks
==3132== Rerun with --leak-check=full to see details of leaked memory
==3132== 
==3132== For counts of detected and suppressed errors, rerun with: -v
==3132== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 37 from 7)
Killed

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

Title:
  indicator-messages crashes and entry call is missed for the user

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  Every now and then, under low coverage circumstances, one call doesn't
  get through to the UI and lets the user know she should be answering.

  Preconditions:
  - Low cellular coverage
  - No connected wifi
  - Some missed calls and one sms in the list of the messaging indicator from earlier

  STEPS to reproduce:
  1. Let the phone sit with black screen on an area with low coverage, with wifi disconnected
  2. Make a call to the phone
  3. The call seems to go through on the calling phone, but ubuntu won't show any sign of it happening.

  See crash file attached from the indicator-messages at the same moment
  this is happening.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-messages 13.10.1+13.10.20130930-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: armhf
  Date: Sun Oct  6 12:09:57 2013
  InstallationDate: Installed on 2013-10-03 (3 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131003)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1234673/+subscriptions


References