I'm going to do some extra tests this weekend and hopefully it's a problem on my end. I showcased the game for 8 hours long on a Macbook Air and didnt run into this problem, that was with the node-webkit export. That one seems to run fine without problems.

Max object count on a stage is about 720 objects. I don't use large images, inspector says 41.4 mb images and runs at 60. Total project consists of 720 events, not every event is for the main game itself.

On four different high end and mid end windows (7 and 8) machines I run into this problem. Also with a laptop that has a clean windows install. My current machine for testing is an i7 2600k with 12 DDR3 and a 7970 with 3GB GDDR5. I will check the vram settings.

Ah I see, so that means as long as that is not going to be fixed, the node-webkit export is not able to make a proper executable that doesn't freeze up?

That is quite a bummer. Is this stuff known? I mean, it seems like a big problem? Because at the moment im not able to release my game in it's current state. I have no idea if this might be fixed in the following weeks/months, so kinda worried now:)

I don't think it's anything to do with Construct 2. AFAIK games run smoothly on other platforms, so it sounds like a node-webkit issue.

Thanks for the quick response. I also don't think it's a problem with Construct2 itself. But is there an alternative export for getting an executable since node-webkit is the only way at the moment as far as I can see?

The freezing is not a huge concern/problem at the moment, but releasing a game in this state is not very desirable.

Edit: After searching a bit more I stumbled upon this post about node-webkit and occasional freezes, might be related? Apparently I cant post urls but I found it on Github: Roger-wang / Node-webkit. The issues title is: NW would freeze occasionally #1363

The issue was closed since it didnt seem related to node-webkit but with js engine's (v8) garbage collection.

This is beyond my skillset/knowledge so I don't know if this is related at all but maybe its usefull to someone here.. Is this something that Construct2 uses? This freezing problem is haunting me at the moment.

Ashley, it looks like there are more people having the same freezing problem. Could it be garbage collection or something after the Node-webkit exporter on windows?

Katala, not only on multiplayer games. Imagine a single player match and you are jumping or trying to do something, but the game froze for 5 seconds. It's really, really bad.

Sorry for bumping this thread up but has this bug been fixed yet with the freezing problem or is there more information out there how to fix this?

With a project i'm currently working on I have a freezing problem and I can't seem to figure out what the problem is and how to fix it. The game freezes at random intervals for about 2 to 4 seconds. When it happens it seems very random and not when a particular event/action is happening. This makes it even harder to find out why it happens. Sometimes it doesnt happen while playing for 10 minutes long but it can also happen after 80 seconds or after 30.

It also depends on which system I play it on, it seems to happen on the windows platform but not on Macs with the node-webkit exporter. Atleast thats my experience so far. I'm starting to think its a problem with the export and with windows. But I can also be totally of about that. Any information is welcome