Construct 2 v269 Closes Randomly

0 favourites
From the Asset Store
Casino? money? who knows? but the target is the same!

    Good to see this topic discussed. WrathOfAbe has put it together what I have experienced so far since R265. Wanted to downgrade but some of my projects were already saved in later versions.

    Was happy to see R277 being released. On my mid-range PC with 8Gigs of Ram it still crashes regularly. But at least it now takes some time. If I have an open browser or other ram swallowing programs running it will crash if I Alt-Tab over to or out of Construct. Sometimes just by clicking something in the editor. Same if I have more instances of Construct running. Always having my fingers crossed when I switch windows. Not exactly... most of the time I forget to save and this makes it pretty annoying. :-p

    Funny thing is right now - it works like a charm. Yesterday I was upset enough to install R265 again and after a while of pondering about I revoked my decision and installed R77 again. Now I have three instances of Construct, one program is test running in NWjs and an open browser with around 20 tabs. Opened the image editor, tabbed over, another image editor (still running?!?) then deleting some frames... writing some words in the forum, switching over and it works, whiskey tango foxtrot?!

    I will test this further but today it looks surprisingly good.

    Hello. Recently, many users of the social network Vkontakte (Russia) have noticed a random crush. If you switch the language (ALT + Shift) in an empty active text field (for example, a comment or variable), then crash occurs. Crush is random and cannot be reproduced in 100% of cases. But this only happens when the field is active. If you make field inactive (for example, click on a sprite), switch the language and make field active, then all normal. This crush works in r272-r277 versions, and don`n works in early version (many users use r265).

    I am still experiencing the issue in r277. I'm working with some big sprites, so the crashes are annoying and frequent. If I provide a CAPX, will meaningful progress be made towards fixing it? Or is it kind of moot at this point? I'd rather not have to downgrade, but it may be the only option.


    In my case the error continues, I simply opened the graph editor, imported a 48x48 graph, changed its control point 0.

    I closed the graphics editor, saved the job in case of a crash.

    The crash occurred.



    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.


    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:


    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.

    I was able to reproduce it

    In this video you can see it.

    1 - Open sprite editor of the test project

    2 - open image points window

    3 - select between the animation frames

    4 - close sprite editor

    5 - press alt + tab and change window

    6 - wait 5 seconds

    7 - C2 closes

    test project

    Version 277 64

    With this bug fixed C2 will die in peace.


    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.


    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.

    It is true, you just have to have the window of the image points open and navigate between the animation frames, It is not necessary to navigate in the image points.

    I have updated video and link of the test project so that anyone can try it.

    Can also reproduce this now on my Windows 10 PC with C2 (Steam). No crash messages or warnings, it's just straight up closing. I think this is it. I never experienced this type of "crash" before, probably because I never use alt+tab.

    Ashley Would appreciate if you could fix this in the next C2 maintenance update.

    I can also reproduce this. Ashley would be great if you could fix this incredibly frustrating issue, or at least confirm that you're working on it in any capacity. Construct 2 isn't retired yet and I would consider this a rather essential bug fix.

    I also can reproduce this. Win 10 64-bit. Non-Steam version.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    I can reproduce the crash following PabloDev's instructions.

    I appreciate everyone trying to figure this out, I read these posts recently and I currently have a habit to save/close C2 after I have opened the animation editor, just in case it sets off a later crash.

    OK, so I finally got round to looking in to this and finally managed to reproduce it. It was a crash in the UI library, but it looked like it came from our code incorrectly cleaning up the Image Points window. I managed to fix that and released an update r278 with the fix. Hopefully that will solve it, let me know how it works for you. And hopefully there aren't any more "random crash" type issues...

    Ok, I did the test and the crash did not occur.

    For me the error seems solved.

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

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