Construct 2 v269 Closes Randomly

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

    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.

    276

    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.

    Ashley

    I THINK I'VE FOUND A CONSISTENT CAUSE

    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.

    TRIGGERING THE CRASH:

    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:

    Laptop

    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

    youtu.be/bCNFJW9GQTs

    test project

    dropbox.com/s/mhhtlrehccihd4e/crashC2.capx

    Version 277 64

    With this bug fixed C2 will die in peace.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    OK

    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.

    OK

    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 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!

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

    Thanks for the update and looking into it. Any idea when this update will hit the Steam version? That one is still on 272, or atleast on my end and it wont update even when I force it to check for updates.

    It's already on the Steam version - as usual it's simultaneously released there. It's a beta release though, so you have to opt in to betas.

    It sounds like the issue is fixed so closing this thread now. This thread has also already involved two unrelated issues, and long threads like this actually make it much harder to deal with issues, since it ends up with loads of sometimes irrelevant or contradictory information. If there are still any remaining issues, please start a new thread and follow all the guidelines from scratch once again since they are probably also unrelated, and make sure you include all the information we need. Adding to this thread for any further issues will only increase confusion and delay.

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