https://bugs.kde.org/show_bug.cgi?id=271934 --- Comment #67 from Oliver Henshaw --- I produced a version of attachment #79569 with glib2 debugging symbols but managed to destroy it by accident before I could attach it to the bug. Anyway the memory increases look like the "possibly lost" reports from attachment #77807 - for example: ==26563== 2,290,528 bytes in 4,618 blocks are possibly lost in loss record 2,488 of 2,488 ==26563== at 0x4C2788A: memalign (vg_replace_malloc.c:727) ==26563== by 0x4C27925: posix_memalign (vg_replace_malloc.c:876) ==26563== by 0xCBE2428: slab_allocator_alloc_chunk (gslice.c:1381) ==26563== by 0xCC29CFA: g_slice_alloc (gslice.c:724) ==26563== by 0xCBECEBD: g_bytes_new_with_free_func (gbytes.c:173) ==26563== by 0xCC3CC0B: g_variant_new_from_trusted (gvariant.c:326) ==26563== by 0x26241825: parse_value_from_blob (gdbusmessage.c:1219) ==26563== by 0x262419F0: parse_value_from_blob (gdbusmessage.c:1439) ==26563== by 0x26241BD3: parse_value_from_blob (gdbusmessage.c:1354) ==26563== by 0x262419F0: parse_value_from_blob (gdbusmessage.c:1439) ==26563== by 0x26243135: g_dbus_message_new_from_blob (gdbusmessage.c:1793) ==26563== by 0x2624D674: _g_dbus_worker_do_read_cb (gdbusprivate.c:753) ==26563== by 0x261EEFB6: g_simple_async_result_complete (gsimpleasyncresult.c:767) ==26563== by 0x261EF0B8: complete_in_idle_cb (gsimpleasyncresult.c:779) ==26563== by 0xCC0F824: g_main_context_dispatch (gmain.c:2539) ==26563== by 0xCC0FB57: g_main_context_iterate.isra.23 (gmain.c:3146) ==26563== by 0xCC0FF51: g_main_loop_run (gmain.c:3340) ==26563== by 0x2624B4D5: gdbus_shared_thread_func (gdbusprivate.c:277) ==26563== by 0xCC32494: g_thread_proxy (gthread.c:801) ==26563== by 0x7BF7D13: start_thread (pthread_create.c:309) ==26563== by 0x96AB68C: clone (clone.S:115) -- You are receiving this mail because: You are watching all bug changes.