Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1EF16431FBD for ; Mon, 3 Feb 2014 10:23:01 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YS6izLEtHfI9 for ; Mon, 3 Feb 2014 10:22:57 -0800 (PST) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 8630B431FBC for ; Mon, 3 Feb 2014 10:22:57 -0800 (PST) Received: by mail-qa0-f44.google.com with SMTP id w5so10740302qac.31 for ; Mon, 03 Feb 2014 10:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=j+c50hMoqJ7TI7SwpNzglz5Y8CQNoJdIA4MXYCJ6oKY=; b=T01sV3g/ZrFfGQ9MpiFPkwg4oLXYSA/Z6q3IsL7n58V4zfqxdjSyrpHYzMW1UpuqPZ LUiYMDOPbl2y7UXMxRwT+ag/HOrwtZnAdHYlwOdxnyb9lGFC0QW8o10uF4aOzTE1FZs0 jn2LhRmtxGqctUpe43hmCLrnWmoNcdgnImDHYfy0bp2aYnutqV5UCuzXRhTj5X6n/OsP 2Z2obrWFZHiGdbMRXsKpuYzxVroCtVny1ptXvUif/Q4//PR1u0Itah2qIil/cIr2SIEM z8OOgZOlCKSJe9NLaOCcxdgnIpR16D/uPMz1uhHuiSEc8+1GrBn0c+NgLBYXejIUxZi0 MaBg== X-Received: by 10.140.43.230 with SMTP id e93mr55902686qga.35.1391451770881; Mon, 03 Feb 2014 10:22:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.49.83 with HTTP; Mon, 3 Feb 2014 10:22:10 -0800 (PST) From: Hamish D Date: Mon, 3 Feb 2014 18:22:10 +0000 Message-ID: Subject: notmuch new crashing due to out of memory - how to deal with it To: notmuch@notmuchmail.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 04 Feb 2014 00:28:10 -0800 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Feb 2014 18:23:01 -0000 Hello I recently deleted almost 30000 old messages from my maildirs, and since I did that, notmuch new has not managed to complete. I have it running on a server with 1 GB of RAM, and the output is telling me Cleaned up 25515 of 29803 messages (1m 10s remaining). at the point it is killed. I have followed it up to this point with top and free and I can see memory usage growing to something like 700MB (RES) at which point the process is killed. I am using notmuch 0.17 (from the debian jessie package) on debian wheezy 64 bit. Any pointers as to what to do to get past this point would be greatly appreciated. If I have just deleted that many messages should I just expect notmuch to use that much memory? I guess I could enable swap and hope that allows enough memory to get past this operation. I did also try running it with NOTMUCH_TALLOC_REPORT, but that didn't produce a report (though I was unsure if I needed to rebuild notmuch before that would work). Happy to build notmuch from source if this might be an interesting bug worth tracking down. Hamish