Closed marilmanen closed 2 years ago
You always have something interesting for me!
This looks like it happened during macro resuming. I'll check it out!
Now I got same core dump again. I also notice that I was not using the latest version, so I'll update to the latest .
Oh yea, please do an update! I couldn't quite nail the cause of this one down, so it's been hard to diagnose. Maybe if we're lucky it's already been fixed, LOL.
So a POSSIBLE fix is in... maybe. Basically I found a spot where during macro execution, legacy nedit was using an uninitialized variable, and NG was simply crashing. It had to do with macro execution when the cursor is not currently visible. So I can imagine a scenario where you've got some delayed macro execution or even a macro executing the background and hitting it.
Since it's not the same exact backtrace, I'm not going to close this issue just yet, but will be cautiously optimistically keeping an eye on it ;-)
I have now the latest version in use, so let's see if I can make it crash :-)
Good luck, You are one of the more reliable "testers" I have, each finding helps!
Closing this since it's unclear if the crash happened with the latest code. Please open a new issue with details if you experience a crash again.
This time crash happened while I was doing something else and I didn't see the actual crash