From 15f042f083a718602977dc19eaf0258eb6f2d455 Mon Sep 17 00:00:00 2001
From: counterpoint <counterpoint@aliro.org>
Date: Mon, 21 Sep 2015 15:49:57 +0100
Subject: [PATCH] On reflection, freeing keys and values in hashtable
 processing is not a good idea because we don't know what they are, and can
 put up with some small memory losses.

---
 server/core/hashtable.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/server/core/hashtable.c b/server/core/hashtable.c
index 4f7620349..7fd45e898 100644
--- a/server/core/hashtable.c
+++ b/server/core/hashtable.c
@@ -763,8 +763,6 @@ char		buf[40];
 		value = valueread(fd);
 		if (key == NULL || value == NULL)
                 {
-                    free(key);
-                    free(value);
                     break;
                 }
 		hashtable_add(table, key, value);