Construct 2 (r267) closes itself randomly.

> Then what about making a beta branch with r265?

What does that actually solve? You can already roll back to r265 if you want. Just download and install it. It won't open projects saved in newer releases, but if you're willing to modify the project file to allow that, then you can already go ahead and do it.

As relixes said, I've meant Steam version. You can't roll back manually, if you're using Steam version of Construct 2.

Ah, I see. (This is the kind of detail that gets lost in long threads...)

I've added a new beta branch on Steam that is fixed to r265 so you can use that to roll back if you want. But that doesn't itself do anything to solve the problem.

Ah, I see. (This is the kind of detail that gets lost in long threads...)

I've added a new beta branch on Steam that is fixed to r265 so you can use that to roll back if you want. But that doesn't itself do anything to solve the problem.

Thanks a lot, really appreciate it!

Ashley thank you so much!

WELL I JUST LOST AN HOURS WORK SO YOU BETTER SORT THIS OUT REAL SOON

I think the problem is with the sprite editor. I begin adding a few animations for one of my sprite(just still images, not animated sequences), when finished I close the editor, save and then open the editor again for another sprite. Construct 2 close without warning at the very moment I double click the sprite.

I think the problem is with the sprite editor. I begin adding a few animations for one of my sprite(just still images, not animated sequences), when finished I close the editor, save and then open the editor again for another sprite. Construct 2 close without warning at the very moment I double click the sprite.

Please upload the project you used for reproduction.

Just to throw in my lot:

I have been experiencing this problem, usually after I close the sprite editor or soon after saving. I am using r268, 64 bit build. I do not have autosave turned on.

However, I think the problem went away since I put all of my objects into folders (i.e. so they are not loose on the projects sidebar). I'll keep an eye out in case I'm way off base, but my wild guess is that this problem is being caused by too many objects on-screen in the projects sidebar, maybe due to a bug in the new version of the 3rd party UI library Ashley referenced.

For other people experiencing the crash, it might be helpful to know if you also have a cluttered projects sidebar.

My objects are also in folders and I experience crashes, so it's probably not that :(

Just to throw in my lot:

I have been experiencing this problem, usually after I close the sprite editor or soon after saving. I am using r268, 64 bit build. I do not have autosave turned on.

However, I think the problem went away since I put all of my objects into folders (i.e. so they are not loose on the projects sidebar). I'll keep an eye out in case I'm way off base, but my wild guess is that this problem is being caused by too many objects on-screen in the projects sidebar, maybe due to a bug in the new version of the 3rd party UI library Ashley referenced.

For other people experiencing the crash, it might be helpful to know if you also have a cluttered projects sidebar.

I got crashed since the 'memory use' get more than 10mb

So here's how it crash from my experience:

- Only happen if memory use >10mb

- If you import many animation or frame (Sprite editor only)

- Alt+tab while layout is active also cause force close

- Saving the project also cause force close occasionally

- Autosave sometimes make force close

- Saving and then close C2, suddenly Force close appear

- If more than 5 layouts on the bar, and you make some changes in event sheet, sometimes also cause force close.

It could be memory related. For me, my project with 107MB memory usage seemingly doesn't crash, but my project with 167MB memory usage does.

Probably not it either, my project uses 29MB and crashes.

Did the crashing just start in r267? If so it's something they did to construct that makes it crash.

Did the crashing just start in r267? If so it's something they did to construct that makes it crash.

Of course. It doesn't happened before so i t has to be related to new changes in the software