Tokinsom would you mind trying the latest git tip? If it still exists, please export it to some URL as describe in above comments and send it to me?

dl.node-webkit.org/live-build/09-06-2014/win64_master-build-173-4beeddf-692f0ab-731b9e2-0f7c844-ae5bb86-86728d1/node-webkit-v0.10.5-pre-win-ia32.zip%3C%3C

— I don't think this bug happens on Linux. Is that correct?

I can reproduce it now on a thinkpad. Here is the build that fixed it, please have a test:

dl.node-webkit.org/live-build/09-04-2014/win64_master-build-164-982168c-1f1810c-731b9e2-0f7c844-c60f60d-86728d1/node-webkit-v0.10.3-win-ia32.zip%3C%3C

I made a new version for diagnostic. If you hit the freeze issue. Please download this, run the executable, navigate to 'chrome://gpu' and post the result here. And also please do the same in Chrome browser and post the result if your game works well in Chrome.

dl.node-webkit.org/live-build/09-02-2014/win64_master-build-161-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-win-ia32.zip%3C%3C

dl.node-webkit.org/live-build/09-02-2014/mac64_master-build-163-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-osx-x64.zip%3C%3C

dl.node-webkit.org/live-build/09-02-2014/linux64_master-build-158-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-linux-x64.tar.gz%3C%3C

SirSpunky

—

Lunatrap

vlweb3d

Giganten

megatronx

A Chrome 35 version I can find is here: >>http://www.oldapps.com/google_chrome.php<<

Lunatrap, I mean you should export your game as HTML, put it to some online place to get an URL. Then make sure the game under the URL works well with Chrome 35, but works badly when you start plain node-webkit and navigate to the URL.

Giganten what about the URL on the same system (where original node-webkit freezes) with Chrome 35? It can be downloaded from

Lunatrap, could you please also prepare an URL as describe in the first post?

I cannot reproduce it with Giganten 's URL. It looks like hardware specific but more cases might be helpful. If I cannot reproduce it in the end, I may have to build a version with some diagnostic feature and then let you run it in your system.

Giganten what's your OS version and hardware? I tried loading the URL in node-webkit here on Mac OS X 10.8 and it works well. Will try it on more Mac and other systems tomorrow.

Hello,

I'm the maintainer of the node-webkit project. Recently I receive 2 issue reports on the integration of C2 and node-webkit. I would like to resolve it soon. But I didn't get much information in the issue page, so I'm looking for help here.

The input lag issue ( github.com/rogerwang/node-webkit/issues/2176 ) is found to be related to a startup argument C2 used in package.json. After removing it the issue is gone. But that leads to another issue about freezing: github.com/rogerwang/node-webkit/issues/1991 , which I need some help here.

Could anyone post a game URL that works well in Chrome 35 (which node-webkit 0.10.x is based on), but works badly in _original_ node-webkit v0.10.2? By "original" I mean you should download node-webkit v0.10.2, launch it without any arguments, and navigate to the game URL. That would help me pinpoint the root cause. Please leave your comments in github.com/rogerwang/node-webkit/issues/1991

And please do the following:

Download this, run the executable, navigate to 'chrome://gpu' and post the result here. And also please do the same in Chrome browser and post the result if your game works well in Chrome.

dl.node-webkit.org/live-build/09-02-2014/win64_master-build-161-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-win-ia32.zip%3C%3C

dl.node-webkit.org/live-build/09-02-2014/mac64_master-build-163-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-osx-x64.zip%3C%3C

dl.node-webkit.org/live-build/09-02-2014/linux64_master-build-158-982168c-8c5bc86-731b9e2-0f7c844-3d94950-86728d1/node-webkit-v0.10.3-linux-x64.tar.gz%3C%3C

Thanks in advance.

Roger

Ashley thanks.

xexeo I tried some code for getUserMedia under a 2-camera configuration but it didn't crash. Anything in plain HTML5 helpful to reproduce it?

We'll see the issue from node-webkit's side. You can track it here: github.com/rogerwang/node-webkit/issues/394