From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 8702E6DE22BC for ; Thu, 29 Mar 2018 05:50:28 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.231 X-Spam-Level: X-Spam-Status: No, score=-0.231 tagged_above=-999 required=5 tests=[AWL=-0.232, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DrWENEuOshq for ; Thu, 29 Mar 2018 05:50:27 -0700 (PDT) Received: from marcos.anarc.at (marcos.anarc.at [206.248.172.91]) by arlo.cworth.org (Postfix) with ESMTPS id 4C3EF6DE206D for ; Thu, 29 Mar 2018 05:50:27 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: anarcat) with ESMTPSA id 2984D10E04F From: =?utf-8?Q?Antoine_Beaupr=C3=A9?= To: Olly Betts , David Bremner Cc: notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org Subject: Re: bug: "no top level messages" crash on Zen email loops In-Reply-To: <20180329031721.GA31208@survex.com> References: <87d10042pu.fsf@curie.anarc.at> <87woy8vx7i.fsf@tesseract.cs.unb.ca> <87a7v42bv9.fsf@curie.anarc.at> <87r2ofx27q.fsf@tesseract.cs.unb.ca> <20180329031721.GA31208@survex.com> Date: Thu, 29 Mar 2018 08:50:22 -0400 Message-ID: <87efk359m9.fsf@curie.anarc.at> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 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: Thu, 29 Mar 2018 12:50:28 -0000 On 2018-03-29 04:17:21, Olly Betts wrote: > On Mon, Mar 19, 2018 at 05:03:21PM -0300, David Bremner wrote: >> I can confirm this reproduces both the xapian-check and the notmuch-show >> error. Olly agrees that whatever notmuch is doing wrong, it shouldn't >> lead to a corrupted database > > There was a Xapian bug here, which I fixed on master last week and will > be fixed in 1.4.6. An honor. It's not every day you find a bug in a database software. ;) > If changes to a new database which didn't modify the termlist table were > committed, then a disk block which had been allocated to be the root > block in the termlist table was leaked (not used but not on the > freelist of blocks the table can recycle). This was largely harmless, > except that it was detected by Database::check() and caused an error. Hmm... but if I understand correctly, that's one part of the story: I could get that error and not have the problem with `notmuch show`. Does that *also* resolve the issue with email loops? A. -- Travail, du latin Tri Palium trois pieux, instrument de torture.