Ticket #87 (defect)
Opened 2 years ago
Last modified 2 years ago
Closure leaked in when dbus call fails
Status: new
| Reported by: | rossburton | Assigned to: | chipx86 |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | libgalago | Version: | 0.5.1 |
| Severity: | normal | Keywords: | |
| Cc: | D-BUS Version: | ||
| Patch Included: | 0 | OS/Distro Version: | |
If I make a call with galago_dbus_send_message_with_reply_async() that then fails and returns an error, the closure allocated is never released.
==23085== 176 (80 direct, 96 indirect) bytes in 4 blocks are definitely lost in loss record 51 of 115 ==23085== at 0x401D9D2: calloc (vg_replace_malloc.c:279) ==23085== by 0x49741D4: g_malloc0 (gmem.c:150) ==23085== by 0x4735DD0: g_closure_new_simple (gclosure.c:97) ==23085== by 0x4737466: g_cclosure_new (gclosure.c:527) ==23085== by 0x40AF8EF: galago_dbus_send_message_with_reply_async (galago-dbus.c:1008) ==23085== by 0x40B8C5C: galago_service_get_account_async (galago-service.c:724)
A decently formatted valgrind report: