invalid valgrind read errors

Bug #929468 reported by Sebastien Bacher on 2012-02-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BAMF
High
Marco Trevisan (Treviño)
GLib
Fix Released
High
Unity
Fix Released
High
Marco Trevisan (Treviño)
bamf (Ubuntu)
High
Marco Trevisan (Treviño)
unity (Ubuntu)
Undecided
Marco Trevisan (Treviño)

Bug Description

Using the current staging trunk packages, starting a guest session with bamfdaemon under valgrind, those errors are listed:

"==21512== Invalid read of size 4
==21512== at 0x48E53EC: g_type_check_instance_is_a (gtype.c:3960)
==21512== by 0x8073F4F: on_view_active_changed (bamf-matcher.c:122)
==21512== by 0x4E7B359: ffi_call_SYSV (in /usr/lib/i386-linux-gnu/libffi.so.6.0.0)
==21512== by 0x4E7B08E: ffi_call (in /usr/lib/i386-linux-gnu/libffi.so.6.0.0)
==21512== by 0x48C3493: g_cclosure_marshal_generic (gclosure.c:1189)
==21512== by 0x48C2F8B: g_closure_invoke (gclosure.c:774)
==21512== by 0x48D4844: signal_emit_unlocked_R (gsignal.c:3302)
==21512== by 0x48DC0C1: g_signal_emit_valist (gsignal.c:3033)
==21512== by 0x6E40967: ???
==21512== Address 0x7a40e38 is 0 bytes inside a block of size 112 free'd
==21512== at 0x402B06C: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21512== by 0x4963B7A: standard_free (gmem.c:98)
==21512== by 0x4963CEF: g_free (gmem.c:252)
==21512== by 0x497811A: g_slice_free1 (gslice.c:1111)
==21512== by 0x48E4401: g_type_free_instance (gtype.c:1937)
==21512== by 0x48C6A7A: g_object_unref (gobject.c:3021)
==21512== by 0x48C453B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85)
==21512== by 0x48C2F8B: g_closure_invoke (gclosure.c:774)
==21512== by 0x48D4844: signal_emit_unlocked_R (gsignal.c:3302)
==21512== by 0x48DC0C1: g_signal_emit_valist (gsignal.c:3033)
==21512==
==21512== Invalid read of size 4
==21512== at 0x47F92C5: call_in_idle_cb (gdbusconnection.c:4678)
==21512== by 0x495B4AF: g_idle_dispatch (gmain.c:4629)
==21512== by 0x495DA49: g_main_context_dispatch (gmain.c:2510)
==21512== by 0x495DE54: g_main_context_iterate.isra.21 (gmain.c:3118)
==21512== by 0x495E29A: g_main_loop_run (gmain.c:3312)
==21512== by 0x4A434D2: (below main) (libc-start.c:226)
==21512== Address 0x7a45c70 is 0 bytes inside a block of size 12 free'd
==21512== at 0x402B06C: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21512== by 0x4963B7A: standard_free (gmem.c:98)
==21512== by 0x4963CEF: g_free (gmem.c:252)
==21512== by 0x47F40EB: exported_interface_free (gdbusconnection.c:3881)
==21512== by 0x494C297: g_hash_table_remove_node (ghash.c:484)
==21512== by 0x494CA19: g_hash_table_remove_internal (ghash.c:1274)
==21512== by 0x47FC93A: g_dbus_connection_unregister_object (gdbusconnection.c:5059)
==21512== by 0x481319A: remove_connection_locked (gdbusinterfaceskeleton.c:739)
==21512== by 0x48148D2: g_dbus_interface_skeleton_unexport (gdbusinterfaceskeleton.c:969)
==21512== by 0x806F89B: bamf_view_dispose (bamf-view.c:681)
==21512== by 0x48C6921: g_object_unref (gobject.c:2971)
==21512== by 0x48C453B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85)
==21512== by 0x48C2F8B: g_closure_invoke (gclosure.c:774)
==21512== by 0x48D4844: signal_emit_unlocked_R (gsignal.c:3302)
==21512== by 0x48DC0C1: g_signal_emit_valist (gsignal.c:3033)
==21512==
==21512== Invalid read of size 4
==21512== at 0x8073F32: on_view_active_changed (bamf-matcher.c:122)
==21512== by 0x807424D: bamf_matcher_register_view (bamf-matcher.c:265)
==21512== by 0x8074FEE: handle_window_opened (bamf-matcher.c:1832)
==21512== by 0x48C5239: g_cclosure_marshal_VOID__OBJECT (gmarshal.c:644)
==21512== by 0x48C2F8B: g_closure_invoke (gclosure.c:774)
==21512== by 0x48D4844: signal_emit_unlocked_R (gsignal.c:3302)
==21512== by 0x48DC0C1: g_signal_emit_valist (gsignal.c:3033)
==21512== Address 0xd918fa0 is 0 bytes inside a block of size 112 free'd
==21512== at 0x402B06C: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21512== by 0x4963B7A: standard_free (gmem.c:98)
==21512== by 0x4963CEF: g_free (gmem.c:252)
==21512== by 0x497811A: g_slice_free1 (gslice.c:1111)
==21512== by 0x48E4401: g_type_free_instance (gtype.c:1937)
==21512== by 0x48C6A7A: g_object_unref (gobject.c:3021)
==21512== by 0x48C453B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85)
==21512== by 0x48C2F8B: g_closure_invoke (gclosure.c:774)
==21512== by 0x48D4844: signal_emit_unlocked_R (gsignal.c:3302)
==21512== by 0x48DC0C1: g_signal_emit_valist (gsignal.c:3033)
==21512== by 0x59B778F: ???"

Related branches

Sebastien Bacher (seb128) wrote :

The version is 0.2.108+bzr437ubuntu0+403

Changed in bamf (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
importance: Undecided → High
status: New → Confirmed
Changed in unity:
importance: Undecided → High
Changed in bamf:
importance: Undecided → High
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in unity:
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
milestone: none → 5.8.0
Omer Akram (om26er) on 2012-03-17
Changed in bamf:
status: New → In Progress
Changed in unity:
status: New → In Progress
Changed in bamf (Ubuntu):
status: Confirmed → In Progress
Changed in glib:
importance: Unknown → High
status: Unknown → Fix Released
Changed in bamf:
status: In Progress → Fix Committed
Changed in unity:
status: In Progress → Fix Committed
Changed in bamf (Ubuntu):
status: In Progress → Fix Committed
Michal Hruby (mhr3) on 2012-03-23
Changed in bamf:
milestone: none → 0.2.116
milestone: 0.2.116 → 0.2.114
Didier Roche (didrocks) on 2012-03-23
Changed in bamf:
status: Fix Committed → Fix Released
Changed in unity:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bamf - 0.2.114-0ubuntu1

---------------
bamf (0.2.114-0ubuntu1) precise-proposed; urgency=low

  * New upstream release.
    - invalid valgrind read errors (LP: #929468)
 -- Didier Roche <email address hidden> Fri, 23 Mar 2012 14:16:41 +0100

Changed in bamf (Ubuntu):
status: Fix Committed → Fix Released
Adolfo Jayme (fitojb) on 2014-01-11
no longer affects: bamf (Ubuntu Quantal)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.