Comment # 22 on bug 1107197 from Adam Mizerski

valgrind: m_mallocfree.c:280 (mk_plain_bszB): Assertion 'bszB != 0' failed.
valgrind: This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.
host stacktrace:
==1533==    at 0x5803D754: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x5803D864: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x5803D9E9: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x5804C00C: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x58004B83: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x58005097: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x58005228: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x5809B0CD: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
==1533==    by 0x580AACB0: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux)
sched status:
  running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 1533)
==1533==    at 0x403077F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==1533==    by 0x4C788D0: g_malloc (gmem.c:99)
==1533==    by 0x4C91C5B: g_memdup (gstrfuncs.c:391)
==1533==    by 0x4C4C6C6: g_bytes_new (gbytes.c:97)
==1533==    by 0x4CA7F43: g_variant_new_from_trusted (gvariant.c:320)
==1533==    by 0x4CA801E: g_variant_new_byte (gvariant.c:410)
==1533==    by 0x4ADFD4F: g_dbus_gvalue_to_gvariant (in
/usr/lib64/libgio-2.0.so.0.5600.2)
==1533==    by 0x174BD3: nm_dbus_utils_get_property (nm-dbus-utils.c:104)
==1533==    by 0x141026: _obj_get_property (nm-dbus-manager.c:897)
==1533==    by 0x142A0F: _nm_dbus_manager_obj_notify (nm-dbus-manager.c:1211)
==1533==    by 0x1744C7: dispatch_properties_changed (nm-dbus-object.c:231)
==1533==    by 0x4BE67F0: g_object_notify_by_pspec (in
/usr/lib64/libgobject-2.0.so.0.5600.2)
==1533==    by 0xB0D6F92: _notify (nm-wifi-ap.c:44)
==1533==    by 0xB0D6F92: nm_wifi_ap_set_strength (nm-wifi-ap.c:289)
==1533==    by 0xB0CED22: periodic_update (nm-device-wifi.c:438)
==1533==    by 0xB0CED68: periodic_update_cb (nm-device-wifi.c:457)
==1533==    by 0x4C73932: g_timeout_dispatch (gmain.c:4649)
==1533==    by 0x4C72EA7: g_main_dispatch (gmain.c:3176)
==1533==    by 0x4C72EA7: g_main_context_dispatch (gmain.c:3829)
==1533==    by 0x4C73297: g_main_context_iterate.isra.26 (gmain.c:3902)
==1533==    by 0x4C73591: g_main_loop_run (gmain.c:4098)
==1533==    by 0x136071: main (main.c:438)
Thread 2: status = VgTs_WaitSys (lwpid 2081)
==1533==    at 0x57B12C9: poll (poll.c:29)
==1533==    by 0x4C73205: g_main_context_poll (gmain.c:4203)
==1533==    by 0x4C73205: g_main_context_iterate.isra.26 (gmain.c:3897)
==1533==    by 0x4C7332B: g_main_context_iteration (gmain.c:3963)
==1533==    by 0x4C73370: glib_worker_main (gmain.c:5772)
==1533==    by 0x4C9AB74: g_thread_proxy (gthread.c:784)
==1533==    by 0x54A9553: start_thread (pthread_create.c:463)
==1533==    by 0x57BBCCE: clone (clone.S:95)
Thread 4: status = VgTs_WaitSys (lwpid 2198)
==1533==    at 0x57B12C9: poll (poll.c:29)
==1533==    by 0x4C73205: g_main_context_poll (gmain.c:4203)
==1533==    by 0x4C73205: g_main_context_iterate.isra.26 (gmain.c:3897)
==1533==    by 0x4C73591: g_main_loop_run (gmain.c:4098)
==1533==    by 0x4AFDA45: ??? (in /usr/lib64/libgio-2.0.so.0.5600.2)
==1533==    by 0x4C9AB74: g_thread_proxy (gthread.c:784)
==1533==    by 0x54A9553: start_thread (pthread_create.c:463)
==1533==    by 0x57BBCCE: clone (clone.S:95)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.