Created attachment 24833 [details] Gabble log Crashed when doing a video call Backtrace #0 0xb7ccbbcb in g_slice_alloc () from /usr/lib/libglib-2.0.so.0 #1 0xb7d5e989 in g_value_array_new () from /usr/lib/libgobject-2.0.so.0 #2 0xb7f6bb22 in _dbus_gvalue_demarshal_message (context=0xbfbc1a30, message=0x866fc00, n_types=3, types=0x866bc50, error=0x0) at dbus-gvalue.c:1249 #3 0xb7f69baf in marshal_dbus_message_to_g_marshaller (closure=0x84da298, return_value=0x0, n_param_values=3, param_values=0x8685908, invocation_hint=0xbfbc1bac, marshal_data=0x0) at dbus-gproxy.c:1662 #4 0xb7d3ac7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #5 0xb7d50e57 in ?? () from /usr/lib/libgobject-2.0.so.0 #6 0xb7d524b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #7 0xb7d52936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #8 0xb7f6ae3f in dbus_g_proxy_manager_filter (connection=0x84ccf38, message=0x866fc00, user_data=0x84d1ff0) at dbus-gproxy.c:1726 #9 0xb7f2f0d5 in dbus_connection_dispatch () from /lib/libdbus-1.so.3 #10 0xb7f616bd in message_queue_dispatch (source=0x84ce8e8, callback=0, user_data=0x0) at dbus-gmain.c:101 #11 0xb7cacb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #12 0xb7cb00eb in ?? () from /usr/lib/libglib-2.0.so.0 #13 0xb7cb05ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #14 0xb7ea8200 in tp_run_connection_manager ( prog_name=0x80cefb4 "telepathy-gabble", version=0x80cfb2a "0.7.26", construct_cm=0x8055c10 <construct_cm>, argc=1, argv=0xbfbc20c4) ---Type <return> to continue, or q <return> to quit--- at run.c:281 #15 0x08055c03 in gabble_main (argc=1, argv=0xbfbc20c4) at gabble.c:76 #16 0x08055b42 in main (argc=6, argv=0x1c) at main.c:27
Created attachment 24834 [details] Empathy log
Can you reproduce this? Crashing in g_slice_alloc suggests earlier memory corruption, and I've seen a bunch of crashes like this recently. If you can reproduce this, could you try to do so with G_SLICE=always-malloc and valgrind?
I believe this was caused by a memory corruption issue I fixed some time ago. Please reopen if you can reproduce this with a recent Gabble. Thanks!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.