On Tue, Sep 07, 2021 at 09:50:05PM -0700, Kevin J. McCarthy wrote:
On Tue, Sep 07, 2021 at 11:45:03PM -0400, Aaron Schrab wrote:At 18:00 -0700 07 Sep 2021, "Kevin J. McCarthy" <ke...@8t8.us> wrote:Are you using $imap_qresync or $imap_condstore?Yes, I have both of those enabled (using dovecot 2.3.16 from Debian unstable as the IMAP server). In at least some of the crashes I believe I've seen messages about QRESYNC failing immediately before; but I generally have mutt running in a tmux window that's set to close when mutt exits so the message is generally only visible very briefly.That gives me some ideas. I'll take a closer look, but I think my fix in commit 74ce032f may have caused some other issues with $imap_qresync.
Yes, it looks like commit 74ce032f was incorrect. I'll need to fix that and make another stable release soon.
However, I haven't been able to figure out the memory error leading to a crash yet. It would be helpful if you could run with ASAN enabled until you get the crash(es). With ASAN you'll need to arrange it so the tmux window doesn't close when mutt crashes so you can read the ASAN report.
To trigger the QRESYNC failure, delete some messages in the mailbox using mutt. Sync and exit the mailbox, wait till there are more new messages in that mailbox and reopen using mutt.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
