Construct 2 v269 Closes Randomly

  • This problem will probably never be solved, I decided to downgrade my C2 and had no more problems.

    I am using version 259.

    If your project was saved in a later version, you can easily change the project to work on older versions, so you have no rational reason to be angry and beg for a solution, as the team is committed to C3 only.

  • Colludium - thanks for the project and repro steps - I could reproduce what you showed in the video, which meant I could finally make some progress on this.

    It looks related to the fact the Properties Bar is cycling through the objects really fast. When the Animations Editor is closed, it refreshes the Project Bar, which involves deleting all the items and recreating them. However as it deletes items it keeps changing the selection to a different item, which in turn updates the Properties Bar, redraws the layout etc. which is slow and probably thrashes CPU & memory. I'm not sure when this started happening - perhaps it was an update to the third-party UI library we use that changed how selections work while deleting items, or maybe it was always there and people only just noticed this specific case.

    Anyway I adjusted the code to make sure it doesn't try to handle selection changes while deleting items, and it doesn't do the cycling through objects any more, is much faster, avoids hanging, and probably avoids spiking the CPU and memory, which may well fix the problem where it crashes in some cases. I guess we will have to wait until the next beta release to verify this though, since it's possible there are different cases involved here. I'll try to get that out in the next couple of weeks (but in an unrelated matter, at the moment we're having to wait for an unexpectedly lengthy certificate renewal before we can issue another C2 update).

    For the record this demonstrates the importance of having a project that reliably reproduces the problem, and is why our bug report guidelines require that. Without any way to reproduce the problem we have no way to investigate it, and the problem can hang around for months. As soon as someone can provide a project that reliably reproduces the problem, we can usually deal with it right away.

  • Ashley - That's great. I'm glad it helped and I hope this resolves the issue for everyone. 👍

  • Our certificate renewal came through, so I've done a new beta release r276 which includes the fix for the issue Colludium reported. Normally I'd avoid doing a Friday release in case any unexpected issues come up but we'll probably be busy next week with a scheduled C3 stable release, so I just went ahead with it now. It'd be interesting to hear if this also clears up the issues others have been reporting.

  • Ashley Thanks for looking into the issue and making a new beta release and also big thanks to Colludium for creating the project that replicated the issue!

    Hope this clears up the other issues as well :)

  • Is anyone who experienced issues in this thread able to confirm if r276 fixed the problem?

  • 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.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • WrathOfAbe - it sounds like you have a reliable way to reproduce a problem in r276. Can you provide a project and the steps to follow as Colludium did? This is the only way we can make progress on this.

  • 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.

  • So far, I haven't experienced a crash since updating.

    Also, the lack of object refreshing after closing an animations window is a god-send for larger projects - I always assumed it was just a quirk of Construct that I had to live with.

  • I am not able to recreate the problem using my desktop PC (i7-6700), only with my laptop (Intel Celeron N4000@1.10GHz).

    It happens more randomly on powerful CPUs, since they are more able to handle the stress.

    On powerful CPUs the crashing depends on how long you use the editor, how many objects you have, size of your project etc. And the time it takes to crash changes from minutes to even hours.

    The only way i can figure out how to recreate the problem every time is to use low-end CPU.

    I tried to make C2 crash on my i7-6700 using the crash.capx provided here (r275), i copied thousands of sprites on one layout and made 100 frames for a sprite, deleted the frames, saved, moved around with ctrl+mouse wheel, but no crash. Maybe if i'd waited for a long time it would eventually crash.

    But with my laptop it crashes everytime.

    Here is a video showing it crashing on my laptop with r276 at 0:35. After that, i'm using r265 with the same laptop, and as you can see, no crash, this also happens everytime.

    https://streamable.com/97n3u

    But it is better now with r276, that much is clear.

  • Thanks for the update and investigation Ashley! It's been a lot smoother going in/out of animation editor, but I've just had the same crash I've always encountered: after 4+ hours of work, last 30 mins were editing lots of sprites and collision boxes, and lots of previews to check the work, then it crashed pressing F4 to preview.

    Following WrathOfAbe, if the machine specs are important, I have an Intel i7-2670 2.20ghz with 12GB of memory. This is a heavy project in terms of events and layouts, with an average of 15 sprites/layout.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)