FS#64365 - [neomutt] Upgrade neomutt (20191025-1 -> 20191102-1) causes double free or corruption coredump

Attached to Project: Community Packages
Opened by Daniel Gray (dngray) - Sunday, 03 November 2019, 04:55 GMT
Last edited by Alad Wenter (Alad) - Tuesday, 19 November 2019, 20:41 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Alad Wenter (Alad)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading when opening you see:


double free or corruption (!prev)
[1] 6126 abort (core dumped) neomutt


Steps to reproduce:
Upgrade neomutt

This task depends upon

Closed by  Alad Wenter (Alad)
Tuesday, 19 November 2019, 20:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  neomutt-20191111-1
Comment by Jonas Witschel (diabonas) - Sunday, 03 November 2019, 09:20 GMT
I cannot reproduce this crash with an empty .neomuttrc or the minimal configuration given in the ArchWiki (https://wiki.archlinux.org/index.php/Mutt#Summary), so either this depends on specific configuration options or something else is broken on your system. Can you temporarily move your ".neomuttrc" to a different location to test with a clean configuration and see whether the error persists, please? If it doesn't, you can successively add back your configuration options to see where the problem is.

Additionally, please add the core dump, obtained by executing "coredumpctl info neomutt", to this bug report since it might contain valuable information to debug the issue.
Comment by Daniel Schömer (quatauta) - Sunday, 03 November 2019, 16:29 GMT
I get the same coredump with neomutt 20191102-1 "double free or corruption (!prev)" when changing to my inbox.

In addition, neomutt segfaults if nm_default_uri is set (set nm_default_uri = "notmuch://$HOME/Mail")
Comment by Daniel Gray (dngray) - Sunday, 03 November 2019, 16:54 GMT
I figured out the issue, turns out it was when I used `` on my mailboxes command ie https://github.com/neomutt/neomutt/commit/f7ef204f9ce33af3a705f586dddd2b27e89ba8fd

Related: https://github.com/neomutt/neomutt/issues/1918
Comment by Jonas Witschel (diabonas) - Sunday, 03 November 2019, 17:22 GMT
Seems like the commit d713c2c in version 20191102 that was supposed to fix the issue #1918 you mentioned is broken. See https://github.com/neomutt/neomutt/issues/1921, in particular the comment by mgedmin (https://github.com/neomutt/neomutt/issues/1921#issuecomment-549130647) for further reference.
Comment by Daniel Martí (mvdan) - Monday, 04 November 2019, 08:53 GMT
neomutt just closes immediately for me when I try to open my inbox. Other folders still work. Running it through valgrind or gdb don't produce anything either; the terminal and shell just exit mysteriously. It's started happening in the last day, so the update is likely to blame too.
Comment by Daniel Martí (mvdan) - Monday, 04 November 2019, 08:54 GMT
Hmm, downgraded to the previous version and the same still happens.
Comment by DaNiMoTh (DaNiMoTh) - Wednesday, 06 November 2019, 08:30 GMT
Hello,

I had the same issue, compiling neomutt from git and using such version resolved the problem.
Comment by Daniel Gray (dngray) - Wednesday, 06 November 2019, 11:06 GMT
Issue https://github.com/neomutt/neomutt/issues/1918 was reopened.

We should test the fix https://github.com/neomutt/neomutt/commit/b486e37c1d5b5ea1b426f844a01c39c2827832dc and let them know so they can issue a bug fix release.
Comment by p4q4d92z (meanmachine) - Thursday, 14 November 2019, 09:13 GMT
I am not sure why and actually can't debug it. This version creates this problems:

1. Only INBOX shown on sidebar (all others are "gone" even if present in my Maildir structure)
2. offlineIMAP returns a strange debug error and keep duplicating a specific email in my Trash.

The problem 1) is restricted to one of the two accounts I have.
Comment by Daniel Gray (dngray) - Thursday, 14 November 2019, 09:28 GMT Comment by p4q4d92z (meanmachine) - Thursday, 14 November 2019, 09:55 GMT
Oh, sorry, I thought it this task was about that version. The version I'm using is actually 20191111.

Anyway, it has to do with my configuration file, probably. Even thought they stayed the same for 24 month, with this update I had to fix things out. Just hope my case is isolate.

Thanks! :)

Loading...