I can also confirm that the error seems fixed for me. Thanks for the fix!

OK

Good to know this works for someone else. When I triggered the crash, I never had to click around in the image points though. Maybe because I always have the image points menu open already(?)

But yes, this getting fixed would leave C2 in a better state. I hope this can help to finally pin down some sort of cause.

Ashley

I THINK I'VE FOUND A CONSISTENT CAUSE

SO... I've been having these "random" crashes very often after finally updating my C2 version from r255 to r277, with C2 closing every 5-10 minutes or so. I have read this entire forum and have noticed similar causes for my crashes, specifically with using alt + tab to switch windows, only for C2 to begin "Not Responding" for a few seconds and then close with no error message/code. I've spent the past 4 hours or so reading this forum and writing a post of my experiences with these crashes. However, while I was writing I was also attempting to troubleshoot the cause of the crashes and I think I found it! At first I thought it was because I was working in a large project with a lot of images/events and it was just too memory intensive, but once I finally narrowed down the cause, I repeated my test on a tiny project and an empty project and it works in both.

TRIGGERING THE CRASH:

1. Open the image editor of any sprite with at least 2 frames and switch between them while the image points menu is open

2. Close the image editor

3. Alt + Tab

I've found that this will crash C2 every time it is done, regardless of project size. Also it only crashes if the image point menu is open when the frame switching is being done.

----------

Not sure if these are needed but just in case, a few general specs:

Laptop

Windows 10

Processor: Intel(R) Core(TM) i7-3520M CPU 2.90GHz 2.90 GHz

RAM: 4.00 GB

----------

So anyway, I hope I can help resolve the issue, sorry for the long post.