Well, some users are having issues with the newest version of node-webkit, but your symptoms sound different. Or...maybe not.
How do you define a 'big freeze'? A few frames? A half second? Many seconds?
Have you tried exporting any of the template game projects that come with C2?
=> I don't know, some of the projects couldn't open due to the version, others did, here I've just created a new project 640x480, I imported 1 object, I added the behavior "move left/right/down/top" then I rendered... And I get freeze with that... it's ridiculous...
I define this big freeze like that:
1- The game opens immediatly
2- The smooth of the screen suggest it's at least 60fps, absolutly no lag
3-When I press a button the object move immediatly, no latency
4-Suddently with no "previous lag frame", the game freeze, the image doesn't move at all.
5- My cpu infos are not frozen (cpu 25% , ram 40% , core to regular temperature) The computer and other stuff work as usual
6-After 3 or 4 seconds (randomly) the game unfreeze and return immediatly to 60fps (extremly smooth)
I tried everything, tomorrow I'll check the app on another computer to check ... my friend has the exact same computer so this is a good reference...
I'm wondering if the game is correctly exported... or if the problem is the "stuff" that runs the game