pidgin: d7eef3ca: Surely this was a mem leak?

[markdoliner at pidgin.im]

-----------------------------------------------------------------
Revision: d7eef3ca41d79b4a297ff1c8b89fb1e9e2912b94
Ancestor: d8be6664f7fa86101932a504becbfe1e313dc8f8
Author: markdoliner at pidgin.im
Date: 2009-10-21T22:28:59
Branch: im.pidgin.pidgin
URL: http://d.pidgin.im/viewmtn/revision/info/d7eef3ca41d79b4a297ff1c8b89fb1e9e2912b94

Modified files:
        libpurple/protocols/jabber/message.c

ChangeLog: 

Surely this was a mem leak?

-------------- next part --------------
============================================================
--- libpurple/protocols/jabber/message.c	7dcf7918d32cd1c64bf9f0c184a4f8dec8e78885
+++ libpurple/protocols/jabber/message.c	2217687932ea32248720b17723455724a0bf5335
@@ -783,6 +783,7 @@ void jabber_message_parse(JabberStream *
 					const char *jid = xmlnode_get_attrib(invite, "from");
 					g_free(jm->to);
 					jm->to = jm->from;
+					g_free(jm->from);
 					jm->from = g_strdup(jid);
 					if((reason = xmlnode_get_child(invite, "reason"))) {
 						g_free(jm->body);