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 C93AA431FAF for ; Mon, 3 Feb 2014 12:14:24 -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 PRvah66rEiN2 for ; Mon, 3 Feb 2014 12:14:20 -0800 (PST) Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 86D16431E64 for ; Mon, 3 Feb 2014 12:14:14 -0800 (PST) Received: by mail-qc0-f170.google.com with SMTP id e9so12319606qcy.29 for ; Mon, 03 Feb 2014 12:14:13 -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=DBJeWxgwVGzPGI813wDGXZhMJ2r6I48Va+o9AKwFc5w=; b=ueMnxjrvpzAKlzKUFb2l5d4zkO6wIKU27pxb1I4KJ8ueMO3OS3oH4gWJaOs6xyKML9 gAESqU6f+/luNe2MdpNYUeigXSwSp2H/5qOs10hyZ/lCkp67Fd6pkJsVS7iZ60r5Sndj cMFp+Beyt+yc/sI1dbPJKNVbmtxK0O3mismfjsp56tccagcy45O2HC7zrqH8aGyPWiND f9blUxwz382NyJZPvFplumEFIriVfLO3mSEpFYcheHayccdyQ1WVn7tZroeLw3uFZt1N Hck5FylDhShuqotGaZV416jk3sqz6mq35aw9Baj0eNBxhwUKTa62X9AUwqQSbdXIblhP S5LA== X-Received: by 10.224.147.75 with SMTP id k11mr59116803qav.22.1391458452825; Mon, 03 Feb 2014 12:14:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.49.83 with HTTP; Mon, 3 Feb 2014 12:13:32 -0800 (PST) From: Hamish D Date: Mon, 3 Feb 2014 20:13:32 +0000 Message-ID: Subject: notmuch killed by out of memory - how to move forward 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 20:14:25 -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. (Just checked and swap is not an option with this host). 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