Since updating from a build based on bcdb61560 (Add %T status format for
$sort_thread_groups., 2021-08-05) to one based on 27e61da56 (Merge
branch 'stable', 2021-08-24) I've been experiencing some sporadic
crashes. After getting coredumps enabled, it seems that there are a
couple of different issues. I've mainly observed both of these when
changing folders, I'm using exclusively IMAP folders and for the
purposes here it's all on a single, local IMAP server.
For the more troublesome one I get the following backtrace. Once this
comes up it will keep crashing when I attempt to change to the same
folder, at least in the short term. Although if I open this folder once
with the old build then switch back to the new build the problem will go
away for awhile.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007fb66d64a536 in __GI_abort () at abort.c:79
#2 0x00007fb66d6a22b8 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7fb66d7b03a4 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007fb66d6a9d0a in malloc_printerr (str=str@entry=0x7fb66d7ae6a2
"realloc(): invalid next size") at malloc.c:5389
#4 0x00007fb66d6adf8c in _int_realloc (av=av@entry=0x7fb66d7e2ba0
<main_arena>, oldp=oldp@entry=0x55e25f67af30, oldsize=oldsize@entry=569616,
nb=569824) at malloc.c:4601
#5 0x00007fb66d6af0e6 in __GI___libc_realloc (oldmem=0x55e25f67af40,
bytes=569808) at malloc.c:3246
#6 0x000055e25c20265f in safe_realloc (ptr=0x55e25e53b408, siz=569808) at
lib.c:176
#7 0x000055e25c1c2eb6 in mx_alloc_memory (ctx=0x55e25e53b3b0) at mx.c:1461
#8 0x000055e25c251854 in imap_read_headers (idata=0x55e25e5f2800,
msn_begin=71193, msn_end=71201, initial_download=1) at message.c:409
#9 0x000055e25c24cae8 in imap_open_mailbox (ctx=0x55e25e53b3b0) at
imap.c:997
#10 0x000055e25c1c069b in mx_open_mailbox (path=0x55e25e43f310
"imaps://a...@pug.qqx.org/L/dev/git", flags=0, pctx=0x0) at mx.c:656
#11 0x000055e25c18926a in mutt_index_menu () at curs_main.c:1433
#12 0x000055e25c1b1dd9 in main (argc=1, argv=0x7fffbf9e51b8,
environ=0x7fffbf9e51d0) at main.c:1380
The other problem seems to occur on line 431 of thread.c:
→· !tmp->fake_thread &&→·→· /* don't match pseudo threads */
With this one, starting mutt again and immediately opening the same
folder appears to work, although it seems likely to appear again soon
after. I don't currently have a core file for this problem, since I
wasn't expecting to be looking at two different problems I was just
using the standard name `core` so the one from the first issue that I
noted overwrote the ones from this issue.
For all of this I have:
set sort="threads"
set sort_aux="date-received"
set sort_thread_groups="last-date-received"
I plan to continue looking for a fix myself, but if anyone else has
ideas I'd be glad to hear them.
