Closed gerazov closed 1 year ago
Hmm... Sorry about that. Thanks for the debugging.
It looks like the header cache is the problem. Try deleting it.
I notice that your NeoMutt has lmdb
built-in.
This is a modern database and much faster than kyotocabinet.
You may also want to consider compression as this can halve the size of the files, e.g.
set header_cache_backend = "lmdb"
set header_cache_compress_level = 18
set header_cache_compress_method = "zstd"
Explanation...
The header cache code stores a binary representation of the structures in memory. This is fast, but risky. If the structures change, bad things happen. We do a LOT of checks to make sure that the on-disk structures matche those in-code, but sometimes it's not enough.
Wow! thanks a million :pray: :pray: :pray:
I couldn't solve this for a while now :sweat_smile:
The header cache for me was in ~/.cache/mutt-wizzard
instead of ~/.cache/mutt
(https://wiki.archlinux.org/title/mutt)
And wow lmdb
is soo much faster :zap: :zap: :zap: - awesome tip :sunglasses: - this should be default!
Expected Behaviour
Neomutt opens folder.
Actual Behaviour
Neomutt crashes.
If NeoMutt crashed, did your OS create a 'coredump' file?
Yes.
Steps to Reproduce
The problem started when syncing the account with
isync
via mutt-wizard and the hard drive filled up. When trying to startneomutt
it now crashes.My gmail folder is opened fine and the same e-mail works fine on my laptop.
I've tried deleting and resyncing the folder which works, but again opening the folder crashes
neomutt
with the message:I've followed https://github.com/neomutt/neomutt/issues/3106 to analyze the coredump and get:
How often does this happen?
When did it start to happen?
NeoMutt Version
Extra Info
Operating System and its version Manjaro Linux 22.1.3
Were you using multiple copies of NeoMutt at once? No
Were you using 'screen' or 'tmux'?
tmux
Is your email local (maildir) or remote (IMAP)? IMAP