proposed fix for memory leak in notmuch restore

diff --git a/af/eb3b99f6a44a04c668d9fdc42e3f1921238f47 b/af/eb3b99f6a44a04c668d9fdc42e3f1921238f47
new file mode 100644 (file)
index 0000000..73ac0bb
--- /dev/null
+++ b/af/eb3b99f6a44a04c668d9fdc42e3f1921238f47
@@ -0,0 +1,57 @@
+Return-Path: <bremner@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id D3135431FC4\r
+       for <notmuch@notmuchmail.org>; Sun, 16 Dec 2012 12:16:56 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id f0PpzuXiTW-P for <notmuch@notmuchmail.org>;\r
+       Sun, 16 Dec 2012 12:16:56 -0800 (PST)\r
+Received: from tesseract.cs.unb.ca (tesseract.cs.unb.ca [131.202.240.238])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 6CB70431FAE\r
+       for <notmuch@notmuchmail.org>; Sun, 16 Dec 2012 12:16:56 -0800 (PST)\r
+Received: from fctnnbsc30w-142167090129.dhcp-dynamic.fibreop.nb.bellaliant.net\r
+       ([142.167.90.129] helo=zancas.localnet)\r
+       by tesseract.cs.unb.ca with esmtpsa\r
+       (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72)\r
+       (envelope-from <bremner@tethera.net>) id 1TkKdo-0007ta-SX\r
+       for notmuch@notmuchmail.org; Sun, 16 Dec 2012 16:16:53 -0400\r
+Received: from bremner by zancas.localnet with local (Exim 4.80)\r
+       (envelope-from <bremner@tethera.net>) id 1TkKdj-00050W-E1\r
+       for notmuch@notmuchmail.org; Sun, 16 Dec 2012 16:16:47 -0400\r
+From: david@tethera.net\r
+To: notmuch@notmuchmail.org\r
+Subject: proposed fix for memory leak in notmuch restore\r
+Date: Sun, 16 Dec 2012 16:16:34 -0400\r
+Message-Id: <1355688997-19164-1-git-send-email-david@tethera.net>\r
+X-Mailer: git-send-email 1.7.10.4\r
+X-Spam_bar: -\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 16 Dec 2012 20:16:57 -0000\r
+\r
+In id:87vcc2q5n2.fsf@nikula.org, Jani points out a memory leak in the\r
+new restore code.  This series is a proposed fix, namely do any\r
+allocation on a temporary talloc context that is destroyed after each\r
+line is processed.\r
+\r
+\r