Node-webkit exe freezing randomly

Bugs will be moved here once resolved.

Post » Sun Feb 16, 2014 5:58 pm

Link to .capx file (required! If link is blocked remove the http and www parts):
Zip containing CAPX and exe
https://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 RAMKatala2014-02-16 18:18:17
B
34
S
9
G
3
Posts: 517
Reputation: 5,206

Post » Mon Feb 17, 2014 4:50 pm

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.
Scirra Founder
B
387
S
230
G
87
Posts: 24,249
Reputation: 192,240

Post » Tue Feb 25, 2014 10:58 am

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?
B
8
S
2
G
1
Posts: 1
Reputation: 1,075

Post » Fri Mar 28, 2014 2:23 pm

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!
B
13
S
2
Posts: 104
Reputation: 1,336

Post » Fri Mar 28, 2014 4:13 pm

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.
B
13
S
2
Posts: 104
Reputation: 1,336

Post » Wed Apr 02, 2014 8:49 pm

Damn i got the same problem, my node webkit export sometimes freeze randomly, is there really no way for me to fix that? :(
B
6
S
2
Posts: 9
Reputation: 493

Post » Wed Apr 02, 2014 9:35 pm

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.
Moderator
B
94
S
33
G
33
Posts: 3,006
Reputation: 27,744

Post » Sun Apr 27, 2014 9:59 pm

B
34
S
9
G
3
Posts: 517
Reputation: 5,206

Post » Tue Aug 19, 2014 12:41 pm




Thank you Katala, this temp fix seems to have worked for me.
B
34
S
5
G
1
Posts: 78
Reputation: 3,397

Post » Tue Aug 19, 2014 12:44 pm

You're welcome @EddyDingDongs , Sadly this is still an issue.
B
34
S
9
G
3
Posts: 517
Reputation: 5,206

Next

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 2 guests