Construct 2 v269 Closes Randomly

> During the testing the following steps seem like a very consistent way of making C2 crash:

> 1. Clone Object Type on Layout

> 2. Paste it in Layout

> 3. Double Click new object.

> 4. Duplicate an animation

> 5. Click new animation

> 6. Add frames from gif or just an empty frame.

> 7. Close Editor

> 8. Save

> 9. Move Windows Taskbar.

> 10. Crash

I tried following these steps 3 times in a row in the same project and it worked fine. However no starting project was provided, so I just used the Ghost Shooter tutorial version and cloned the player.

I'm afraid unless there's a way I can observe the issue, which is best achieved by finding reliable steps to reproduce the problem, then it will be extremely difficult to make any progress on this issue.

This problem usually happens when there are sprites with many animations on the screen.

Just now "here in Brazil" in less than 30 minutes, closed 3 times exactly when I sent save.

I have plenty of setup to work with any project in the engine.

Working on a pixel art project, I don't even remember how many times it closed, but in the "images are much bigger" vector project, it closes several times.

Once again, it's difficult to make progress if people don't mention which version they are using. The latest version is r274. Did you test that version? Is it still occurring there or is it fixed?

Once again, it's difficult to make progress if people don't mention which version they are using. The latest version is r274. Did you test that version? Is it still occurring there or is it fixed?

I am using version 272

Watch the video

I updated Construct 2 to beta 274 and the same problem happened, in both videos I used the same project and did the exact same thing and on the first try Construct 2 was closed.

Watch the video

So I hope it is clear where the problem occurs and can be resolved, it is very annoying that this problem has arisen in recent months and several times lost a lot of time to redo because the engine closed out of nowhere.

I hope this is not a deliberate mistake to force people to migrate to C3.

Just want to second the above experience — pressing alt-tab while a large project is saving, or just after, usually crashes here.

Saving doesn't always show a progress bar for me, so I can't tell when the saving is complete, but if I just wait a few seconds after saving before running the preview or switching applications, it's all good.

(using latest Construct beta 274, applies to last few versions as well)

Using version 250 the engine did not close alone again.

Once again I must repeat that without providing a project and reliable steps to follow to demonstrate the issue, it is unlikely any progress will be made on this.

Can confirm what others are saying. C2 started crashing frequently and randomly since I moved from v266 to v267 (64 bit, windows 10, 16GB, Intel Core i5 9600K, Geforce GTX 1060, Chrome 73.0.3683.103). Have tried every version since v267 and they all have the same issue including v275.

Seems to crash more frequently the larger the project. Crashes happen everywhere. On closing image editor, on copying/pasting, alt/tabbing, on double clicking events. Nothing to pin the issue down or recreate so cannot provide steps. The only new information I can provide is that the debug log captures the following errors:

[0303/115842:ERROR:registration_protocol_win.cc(53)] CreateFile: The system cannot find the path specified. (0x3)

[0311/135020:ERROR:crash_report_database_win.cc(549)] CreateDirectory C:\Users\Ashley\AppData\Local\User Data\Crashpad:

[0303/115842:ERROR:crashpad_client_win.cc(316)] CreateProcess: The system cannot find the file specified. (0x2)

[0201/131359:INFO:nw_package.cc(175)] "C:\Program Files\NWjsForC2\win32\nw.exe" --ignore-gpu-blacklist "C:\Users\Ashley\AppData\Local\Temp\c2-302ZR0\html5\package.zip"

[0201/131359:ERROR:image_metadata_extractor.cc(112)] Couldn't load libexif. 126

Ashley, is this helpful?

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?

terence - I'm afraid not: once again, without providing a project and reliable steps to follow to demonstrate the issue, it is unlikely any progress will be made on this. Also the debug log you provided appears to be for the NW.js runtime, which has nothing to do with the C2 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.

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.

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 also get the same crash following the instructions above. I'll take a look at the larger / sprite-heavy projects I have to see if anything similar happens when it crashes. Thanks for assembling that example Colludium!