Not completely. But it seems to be better now.

I tested with the crashes.capx on my very low-end laptop, to see what is the difference between r276 and r265.

With r276, i had about 500 large sprites on layout,then opened editor and duplicated few frames, then deleted them, then exited the editor and saved,and while it was saving, i moved around with ctrl+mouse wheel, it crashed every time.

With r265, C2 was unresponding for a moment, but always recovers and never crashes.

With my high-end desktop PC (r276), it crashes, but not as often as it used to.

Yesterday i had 2 crashes, today 1. On both days i worked around 6 hours, using the editor occassionally.

Earlier today i tried to make it crash using my project, which is 22mb in size and has a lot of sprites, between 600-800 per layout, and i did manage to make it crash by quickly deleting 40 frames from one sprite, then exiting the editor, saving, and moving around with ctrl+mouse wheel.

If you have a low or mid end PC or laptop, you can make C2 more easily crash, and with high-end PCs it might take a while before it crashes, but eventually it will.

Before r276 it crashed in 1 to 10 minutes after using the editor.

Now it seems that it may take a very long time for the crash to occur.

Do not try to make it crash with very small project + high-end CPU, it most likely won't work, since there is not enough stress on the CPU with small project. Use low-end PC or laptop if you have one. And have a big project with a lot of sprites and frames.

Try also having a lot of objects on layout, so that saving takes a bit of time, and is not instant.

The reason why with some people it crashes instantly, and with others takes a while, is the differences in peoples CPUs!

If you have not altered the editors code since autumn 2018, it must be the third-party plugin the editor uses.

Talk with the creators of the plugin, maybe they are not aware of the problem.

You can send it privately if it is a personal project that you do not want to make available to the public.

This is annoying to configure every time you open the project.

I said that I would not insist more but I changed my mind since it is annoying to have to reconfigure when you open a project.

Is it a lot of work to solve this?

Follow without a comment for this error

But that ... if the object is in fall then it should not be able to ascend to a platform.

How difficult is it to solve that in the engine?

I have created a project example that repeatedly demonstrates this crash.

Here's what it looks like. If you've lost work to this then you might want to look away... ;)

Click to play if it doesn't do so automatically:

Here's the project caproj:

Crash test .caproj project

Steps to reproduce:

1) Open the project. Be patient, it can take a minute...

2) Edit any sprite using the "Animations: Edit" in the properties bar (note, the open layout has no sprites in it, so memory use for this project is at a minimum).

3) Close the sprite editor. If you're prepared to wait a minute then it might recover, but if you click on anything / try to close it again / click anywhere else then it'll drag up the windows crash popup.

Things to note. C2 is using approx 152 Mb of memory with this layout open in the editor. After the crash and selection of "wait for the program to respond" then the reported memory use goes down to 20 Mb. Although C2 appears to have recovered, clearly it is not working properly...

What's with the cycling through 150 sprites or so after initially closing the sprite editor...?

Anyway, Ashley, I hope that this is what you need and it'll repeatably crash on your super-computer.

I was able to reproduce it but I am not sure it is the same crash that we have experienced most ... I am not sure.

My project is quite small and had many crashes with the sprite editor.

Just to say, for some reason I didn't get a single crash since I'm using r275.

Not sure anything has changed in the editor or if it is my computer but I used C2 for long periods (hours) and it has been completely stable.

Anyone else noticed this?

I have not had blockages so far but I have not used the sprite editor, previously the blockages, in my case, occurred when I used the sprite editor.

Why don't you ask in the official photon thread? There you will receive a more conscientious answer from one of the photon developers.

I think C2 and C3 use NWjs to export exe.

So it is not possible that it has been solved in C3 and not in C2, I am not sure at all, to see if anyone can provide more information.