Ashley Per your request I'm making a new thread about this since the old one is irrelevant at this point and you are right, its pointless to pile onto that thread about v267 since that isn't the current version anyway.
I'll do my best to describe the problem. I know the Construct team is looking for a concise answer on what is causing this but after reading through the previous thread about v267 I've come to the conclusion that no one really knows what is causing it because the problem cannot be consistently reproduced.
So here goes, I'm currently using Construct 2 v269, the non-steam version. At random intervals the program crashes. I won't comment on if it happened before v269 because I honestly don't know and I don't want to confuse the issue. I can usually tell it is about to happen because C2 will become unresponsive for about 3 seconds or so and then close with no messages about what happened. Below are the times that I have had this happen to me. I will obviously say that Construct 2 does not close itself out every single time you perform one of these actions, but these do seem to be the operations that trigger the problem.
1. Auto-save: Personally, I disabled auto-save a while ago because there was about about a 1 in 4 chance that the game would finish auto-saving then stall for a second, then close. It clearly finishing performing the auto-save because I could go to the auto-save file and it would be up to date. This seemed to be the most consistent thing that crashed C2.
2. Image-Editing: When using the image editor C2 would work fine until you closed the editor. So you could upload or add an image in, do your editing, make more frames etc, all no problem. Once you closed the editor there was a chance, again not consistent, that C2 would just close itself out.
3. Copy-Paste: Copy-Paste in pretty much any setting (excluding the image editor) seems to cause issues. By any situation I mean copying events or actions, or something like making a duplicate of an object in the project bar. I will say in this case using the copy command (Ctrl+C) never seems to crash C2. It's when you paste something you copied that C2 crashes. Again as usual you will hit (Ctrl+V) the game will stall for a second without pasting anything and then crash. As for duplicating objects you click "duplicate" and then it stalls and closes without making the copy.
Those three things are the only things I know of that crash C2 on a regular basis, perhaps there are others but I'd rather not muddy the waters any more than they already are. At the moment I am working in C2 about 8 hours a day and I'd say I see anywhere from 2 to 4 crashes a day. I've basically just started quick saving like I'm playing Skyrim to avoid losing work at this point. If people reply to this thread saying other things crash C2 you may put some stock in it. Its possible that other things crash the program but, if you are willing to take me at my word, these are the things I can see really causing an issue. I know you don't want to go on a wild goose chase through the engine, but it is basically making C2 unusable at this point.
For my own thoughts, if you want to hear them, it seems like something is being bogged down in the engine. The capx I am working with is 7,222kb, suffice to say its got a lot of events and sprites and things. Perhaps this has nothing to do with it but it seems to me that the engine is either hitting an error that doesn't hav a catch somewhere in the code, or there is something about larger projects that it can't handle. That's a shot in the dark obviously. My only other guess is the inconsistency in the problem could suggest something like a memory leak in the code or something that builds up over time, or maybe its something to do with how C2 uses RAM. Based on what I've read and my own experiences C2 never crashes quickly after launching it. It always seems to be something that happens after an hour or two, and once it closes and reopens you get another good amount of time out of it. All three of the triggers described above would likely take a more sizable chunk of memory to perform the actions so maybe its something to do with how it handles memory on a larger scale, sorry I know that's not really much help.
In any case I've already wrote more than people want to read. I'll probably jump ship to C3 soon, but I figured I should put in my two cents before I do, maybe it will help the people sticking with C2. On a final note, I know these are supposed to have a capx attached. The only capx I have is the game I've been working on for about a year so I'd rather not post it publicly. If you have some way I can send it to you privately I'd be happy to do so, although like I said before it seems that this problem can't be reproduced consistently so I don't know how much it would help you. Not to mention you need to be actively working for a while before the game will crash. In any case thanks for looking into this I know a lot of people want this fixed but I understand asking someone to tear through an engine to look for one problem that can't even be clearly identified is nearly impossible.
As one last thing, and I'm sure you have people to do this for you anyway but I figure I'll offer. If you have some sort of terminal like program that monitors C2 as it runs and records everything C2 is doing that might show where it is crashing. If you have some sort of development program like that I'd be more than happy to attach it to my C2 and send you the logs. Obviously, that's hypothetical based on if C2 even has that, in my experience a lot of programs have a system for debugging so I thought I'd mention it. Anyway, good luck, and thanks.