I applied the patch and used it for a few hours. So far so good. No crashes. Yay!
On Thu Nov 26, 2020 at 7:36 AM CET, ~labrat wrote:
~inwit and ~coder_kalyan please apply https://lists.sr.ht/~sircmpwn/aerc /%3C20201126063402.502986-1-reto%40labrat.space%3E and tell me if you notice any improvement...
Look Ma', no magic!
-- View on the web: https://todo.sr.ht/~sircmpwn/aerc2/471#event-59210
notmuch crashes randomly
Here's the traceback: https://paste.sr.ht/~inwit/ec584efbd91bd0613ccc0ac4070ea07ecbd06b90
I'm trying to create a ticket via email for random crashes I'm experiencing. However, when I try to paste the traceback into the mail, aerc crashes again on me with the following traceback:
/usr/local/src/aerc/widgets/terminal.go:142 +0x86 fp=0xc000263fd0 sp=0xc000263f60 pc=0x939b76 created by git.sr.ht/~sircmpwn/aerc/widgets.NewTerminal /usr/local/src/aerc/widgets/terminal.go:124 +0xf7 [signal SIGSEGV: segmentation violation code=0x2 addr=0x7f7e280ac000 pc=0x7f7e76f09963] runtime stack: runtime.throw(0xad21e8, 0x2a) /usr/lib/go-1.13/src/runtime/panic.go:774 +0x72 runtime.sigpanic() /usr/lib/go-1.13/src/runtime/signal_unix.go:378 +0x47c
I wrote this ticket in the web interface, since it is impossible for me to paste the traceback in aerc. I can't do the same for the traceback corresponding to the random crashes, since the text box is limited and my traceback won't fit.
I attach a log file for stdout.
It's not really crashing, but that tab becomes unusable and I have to restart in order to use it. I wrote stderr to a file and the file is empty.
-- View on the web: https://todo.sr.ht/~sircmpwn/aerc2/469#event-58815
With a big M$ IMAP account with many folders, aerc crashes on me if I try to change folders (with repeated use of next-folder and prev-folder), and I believe that it has to do with me going faster than aerc. When I do that, I get a broken pipe. When that happens, the account tab becomes unresponsive and I can only exit and relaunch.
If I can provide more info, please let me know how to do that.