Crash on stepping to next unread

Jaimie

While using, pressed n to go to next unread, got a crash. Restarting showed no problems with that particular message, all working fine again.
Partial crash log (64k message limit!):

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'

Andre

Jamie, I've removed most of the error log for your privacy. It also makes this thread more readable 🙂
Crash reports are very informative to locate the error, but you can better send them to me by email.

I'll locate the error and fix it.

Thanks.

Andre

Can you remember if you did open/close a window just before the app crashed?

Jaimie

Andre I didn't - I'd cmd-k'd, then clicked in a sub and hit n to read two or three messages. Then I clicked in another sub, hit n, hit n again, and crash. Definitely no windows created, and no window resizing or sub-pane resizing.
I wouldn't even have been doing a drag-select if that's what "drag regions" refers to, my mouse-hand would have been inactive while I was reading with n.
Alan - first crash I've had with Usenapp 🙂 Not surprised it's not easily replicable.

Alan_B

I spent quite a bit of time trying to reproduce what Jaimie saw but have failed miserably! I guess it must be a very obscure fault? I remember Usenapp crashing on me when it was first put out to test but I ignored it as no-one else reported it - silly me perhaps!

Andre

Ok thanks, I think you've pointed me into the right direction with your answer.

Andre

Finally fixed in v0.65.6