Node-webkit exe freezing randomly

Link to .capx file (required! If link is blocked remove the http and www parts):

Zip containing CAPX and exe

dl.dropboxusercontent.com/u/104893773/just%20a%20box/just%20a%20box.zip

Steps to reproduce:

1. Run exe

2. Wait it to freeze for few seconds

3. If not.. maybe something to do with my specs

Observed result:

Freezes randomly for few seconds when running

Expected result:

No freezing

Browsers affected:

Chrome: no (not relevant)

Firefox: no (not relevant)

Internet Explorer: not tested

Operating system & service pack:

Windows 7 Ultimate SP1

Construct 2 version:

161 (64-bit)

Also if it helps here are some additional specs

Intel Core i5 3570K (Ivy Bridge)

GeForce GTX 560 Ti

8 GB RAM

Closing as most likely just garbage collection or JIT compilation. I'm afraid it's just something you have to live with, it shouldn't happen after the game has been running 30sec or so. Try using asm.js physics instead.

The same is happen with me. I tried use box2d web, asm.js, cocoonjs native and differents setup, but does work, still freezes. Whats the problem?

Guys, I have the same problem here. I tried different browsers/setups, some of them freeze less than others, but it still freezing. Using Chrome or Node-webkit on preview, or running the exported game on a Mac computer using Node-webkit, works very well and doesn't freeze at all. I think it is a problem on the windows exporter. I tried all the browser setups and I think that the freeze happens more often on IE and Firefox, but it still happening less often on Chrome.

Did you guys find a solution so far?

Thanks!

I tested the game using the Construct 2 profiler debugger mode using Firefox as browser. It didn't freeze at all. Of course the performance isn't as good as the exe version, but at least there is no freeze.

Damn i got the same problem, my node webkit export sometimes freeze randomly, is there really no way for me to fix that?

If it isn't the JavaScript compiling, perhaps you're using too much RAM/VRAM somewhere. I had a problem with my game freezing, only to discover it was because I had accidentally tried to shove 5 gigs of image data into my computer's 2 GB RAM/ 512 mb VRAM and node webkit was swapping data to disk to try to manage it all, freezing the game while it did so.

There seems to be at least a temporary fix here

https://www.scirra.com/forum/two-node-webkit-problems-still-on-v-168-temp-freeze-fix_t95506

There seems to be at least a temporary fix here

https://www.scirra.com/forum/two-node-webkit-problems-still-on-v-168-temp-freeze-fix_t95506

Thank you Katala, this temp fix seems to have worked for me.

You're welcome EddyDingDongs , Sadly this is still an issue.

You're welcome EddyDingDongs , Sadly this is still an issue.

Yeah tell me about it lol

Until I read your post I was freaking the hell out!!! Becos after 5-years of using a crappy lappy I finally bought a new semi-high-end desktop PC, and on this PC I can run Watch Dogs at 1080p on ULTRA graphics settings, and yet on this same PC my extremely simple C2 game is stuttering as though it was some game from the year 2020 running at 4K resolution!

Having exactly the same issue. Starts freezing after a couple of seconds. I got the latest stable release

This nodewebkit thing has been going on for some time now. It seams they can't, won't, or don't care about fixing it. The inherent dilemma of third party components.....

See here:

Thanks Katala that worked for me too!