diff libpurple/protocols/msn/slpcall.c @ 17137:8ed7b2d32ad1

slpcall now explicitlt references its xfer and unreferences it when it is destroyed. While it *looks* like this should *probably* have happened anyways due to the interactins between xfer_init, xfer_end, and xfer_cancel_remote, having the xfer's owner make this explicit makes the process less fragile and more obvious, and it may fix a crash as the slp is destroyed. Fixes #1070
author Evan Schoenberg <evan.s@dreskin.net>
date Thu, 17 May 2007 14:32:24 +0000
parents 0b7110b9e368
children 44b4e8bd759b 0f6747c5dcc2
line wrap: on
line diff
--- a/libpurple/protocols/msn/slpcall.c	Thu May 17 14:30:48 2007 +0000
+++ b/libpurple/protocols/msn/slpcall.c	Thu May 17 14:32:24 2007 +0000
@@ -120,6 +120,9 @@
 	if (slpcall->end_cb != NULL)
 		slpcall->end_cb(slpcall, session);
 
+	if (slpcall->xfer != NULL)
+		purple_xfer_unref(slpcall->xfer);
+
 	g_free(slpcall);
 }