Two Node-webkit problems still on v.168 [Temp Freeze fix!]

Ashley So we're did some tests, and we see that the freezing only appears on exported project, but in preview mode NWK works fine. Any thoughts?

Also can anyone with Win32 can confirm they are experiencing same issue? It might be win64 only thing.

scaffa megatronx

Did you tried to pack to node-webkit yourself? Export from C2 as a normal html5 and then download node-webkit from https://github.com/rogerwang/node-webkit and pack it yourself. It's very easy. Did that some time ago because I don't like how C2 exports to node-webkit - it saves a file package.nw which is basically zipped file with your project inside (all graphic files, sounds, source code etc..) But was doing that on very specific project, where speed or freezes doesn't really matter.

But this could be a nice comparison if this is something that C2 is doing on export or node-webkit itself while packing the app.

scaffa megatronx

Did you tried to pack to node-webkit yourself? Export from C2 as a normal html5 and then download node-webkit from https://github.com/rogerwang/node-webkit and pack it yourself. It's very easy. Did that some time ago because I don't like how C2 exports to node-webkit - it saves a file package.nw which is basically zipped file with your project inside (all graphic files, sounds, source code etc..) But was doing that on very specific project, where speed or freezes doesn't really matter.

But this could be a nice comparison if this is something that C2 is doing on export or node-webkit itself while packing the app.

Yeah was thinking about that. I'm not really felling confident enough in trying this. But I guess I have no choice, ha!

Any tip on how to do it aside from exporting as standard html5 app?

EDIT@ I've just extracted the package with winrar, removed package.nw, and run the exe, and it's working. Will see if its still freezing.

EDIT2@ Still Freezing

I also never had problems on preview only on exe. I have tried to export on one other pc and same thing. What is really annoying is that there are few games other people made that doesn't have that problem, one is Airscape

Also scaffa s CAPX froze.

I will try shinkans method.

Can't seem to run it, don't really understand how this works Made a package.nw and when I try to run it it says

[quote:3hmrael5]Exported games won't work until you upload them. (When running on the file:///protocol, browsers block many features from working for security reasons.).

I still have no idea what this could be. I think VRAM is ruled out by small projects doing it, and V8 garbage collection is ruled out by the fact Chrome has the same javascript engine, but doesn't reproduce the problem. I think export-mode only is probably not actually the case - the export-time optimisations usually help improve performance and there's really absolutely nothing in the export process that could cause long pauses, so I feel it is more likely it is a sporadic issue that has not been observed in preview mode only by chance (perhaps because people spend less time in preview and more time in exported games?). 4 seconds is also an extraordinarily long pause for any local activity: not even garbage collection covering hundreds of megabytes of memory, or very large disk accesses, would take that long. It might even possibly somehow be a blocking network request.

I would guess the most likely cause is the node.js component of node-webkit, since node-webkit is more or less identical to Chrome apart from in that regard, but that is out of our control and something the node-webkit developers should look at. It's also totally impractical to debug a sporadic issue that only reproduces after ~20min - debugging often involves running and testing the issue 10, 20, 30 times or more, and hours of sitting around watching a game does not sound like it would get anywhere. I think the best approach is to report the issue to the node-webkit bug tracker with (as always) as much information as you can possibly provide, and see what their view on it is.

Node-webkit is also now two versions behind Chrome; it may be the latest version of Chrome has performance improvements which node-webkit will also get when it catches up.

I still have no idea what this could be. I think VRAM is ruled out by small projects doing it, and V8 garbage collection is ruled out by the fact Chrome has the same javascript engine, but doesn't reproduce the problem. I think export-mode only is probably not actually the case - the export-time optimisations usually help improve performance and there's really absolutely nothing in the export process that could cause long pauses, so I feel it is more likely it is a sporadic issue that has not been observed in preview mode only by chance (perhaps because people spend less time in preview and more time in exported games?). 4 seconds is also an extraordinarily long pause for any local activity: not even garbage collection covering hundreds of megabytes of memory, or very large disk accesses, would take that long. It might even possibly somehow be a blocking network request.

I would guess the most likely cause is the node.js component of node-webkit, since node-webkit is more or less identical to Chrome apart from in that regard, but that is out of our control and something the node-webkit developers should look at. It's also totally impractical to debug a sporadic issue that only reproduces after ~20min - debugging often involves running and testing the issue 10, 20, 30 times or more, and hours of sitting around watching a game does not sound like it would get anywhere. I think the best approach is to report the issue to the node-webkit bug tracker with (as always) as much information as you can possibly provide, and see what their view on it is.

Node-webkit is also now two versions behind Chrome; it may be the latest version of Chrome has performance improvements which node-webkit will also get when it catches up.

It's not always after 20 mins, to be fair. Sometimes much quicker. For me it can stop for about 5 seconds too.

But why it never happens on previews? I tend to run preview on second screen sometimes for an hour or so and no hiccups at all!

Maybe I did something wrong. I got the same message as scaffa ,but it started anyway and it froze as well maybe less than 2 min of running and it was about as long as on scaffas video.

[quote:360tqoe1](perhaps because people spend less time in preview and more time in exported games?).

I have spend extensive amount of time testing on Node-Webkit preview and never had this issue. Usually I get first freeze way before 20 min mark on exported game.

I exported the game as I normally would do and downloaded node-webkit-v0.8.0-win-ia32. I used the package.nw from the export and dragged it to the nw.exe to get it running. After 40 minutes I have not experienced any freezing.

Going to keep it running to see where it goes. After 12 hours of testing today I think I need to do something else soon..

I downloaded 0.8.0 since I read a post with someone that had freeze problems with 0.8.1.

I would like to report it to the node-webkit bugtracker but my technical knowledge of this stuff is very limited so I don't think I can provide them with much or usefull information sadly. Hope this will see a fix someday.

I exported the game as I normally would do and downloaded node-webkit-v0.8.0-win-ia32. I used the package.nw from the export and dragged it to the nw.exe to get it running. After 40 minutes I have not experienced any freezing.

Going to keep it running to see where it goes. After 12 hours of testing today I think I need to do something else soon..

I downloaded 0.8.0 since I read a post with someone that had freeze problems with 0.8.1.

I would like to report it to the node-webkit bugtracker but my technical knowledge of this stuff is very limited so I don't think I can provide them with much or usefull information sadly. Hope this will see a fix someday.

will try

Edit THere is 0.9.2 version but i still cant find where i can download the exe from?

You will need to look for the Prebuilt binaries, it's about half way on the site. There is also a link there to older versions under 'Looking for older versions?'.

I cant post a link sadly

You will need to look for the Prebuilt binaries, it's about half way on the site. There is also a link there to older versions under 'Looking for older versions?'.

I cant post a link sadly

OK. I found 0.8.0. Running it for several minutes already, and straight away the performance is smoother! Previously your blocks would slow down and overall pattern would change, but now they constantly in the same pattern! wtf?

btw, you can post links like that. https:// s3. amazonaws. com/ node-webkit/ v0.8.0/ node-webkit-v0.8.0-win-ia32.zip

Ah yeah of course I can post a link like that, doh. Thanks Yeah the physics and thus the pattern change a bit when there is a slowdown, that is also what I notice a lot during testing.

1 hour of testing and still no freeze. Also testing on my tablet (Surface) now. I hope this is a proper fix

Ah yeah of course I can post a link like that, doh. Thanks Yeah the physics and thus the pattern change a bit when there is a slowdown, that is also what I notice a lot during testing.

1 hour of testing and still no freeze. Also testing on my tablet (Surface) now. I hope this is a proper fix

Me too, for almost an hour. No freezing!

So, you have solved that case! Congrats and thanks!

For anyone who's suffering from NWK freezes after exporting, try reverting back to 0.8.0, as it is working for us.

LINK:

At this time it is on the front page under downloads and Prebuilt binaries

https://github.com/rogerwang/node-webkit

Remove your game.exe, extract the file to your node-webkit exported project (replace remaining files ), and that's it! You can rename the exe file.

Ashley Katala Arima shinkan

Katala Please place this post in your first post, to make it easier to find. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile"> You can replace link with latest working version!