Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on pressing any key after startup #515

Open
rwh21 opened this issue Jun 17, 2016 · 2 comments
Open

Crash on pressing any key after startup #515

rwh21 opened this issue Jun 17, 2016 · 2 comments

Comments

@rwh21
Copy link

rwh21 commented Jun 17, 2016

I started sup after not having used it for a couple of weeks. I have it configured to run 'offlineimap' on every poll, and there were approximately 350 new messages on the IMAP server. sup ran offlineimap, and I could see the new messages appearing in the index. When the synchronisation was complete, I pressed the 'Home' key, and sup immediately crashed and produced the attached exception-log.txt.

exception-log.txt

I tried starting sup again. It no longer showed any messages in the index, but said "Searching for threads" at the bottom of the page. When I pressed the up arrow key sup crashed and produced the attached exception-log-2.txt. I tried this again a couple of times. I found that it crashed whatever key I pressed.

exception-log-2.txt

The next time, I started sup and left it saying "Searching for threads". Eventually after 1 or 2 minutes it displayed the list of messages. I can navigate and view the first page of messages. However if I hit "Page Down" on the message index several times, to see older messages, sup crashes and produces exception-log-2.txt.

@jacksingleton
Copy link

I also have this issue. As a work around I've removed this hard fail in index.rb:

https://github.com/sup-heliotrope/sup/blob/develop/lib/sup/index.rb#L628

(literally just removed that line)

The rest of the code seems resilient to that function returning nil. I'm sure there's some bigger problem here, but failing to process one message is much better failure behavior than crashing the whole application and preventing me from reading any of my email :)

@schanzen
Copy link

This is still an issue for me today. I just hit it for unknown reasons.
Sup just crashed out of nowhere and not refuses to start up with the logs from the OP.
The fix above works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants