-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v0.18.1] --single-process Is Not Working Properly #5389
Comments
Could you please provide a sample? |
@rogerwang surething here you go (it's in package.nw format): package.zip |
Thanks. It appears that '--single-process' is only working with command line argument now. Will fix it. |
Good news, thanks a lot. |
@rogerwang I still have the issue on nw.js0.18.2; tested with the file from TheRealDannyyy with nw.js0.18.1 and 0.18.2 (ia32 and x64 from https://dl.nwjs.io/ ) on win7Pro-64b and Win8.1Pro-64b |
This is fixed in git and will be available in the next nightly build. |
@rogerwang is there any ETA for when this will go stable? |
The next release is in a week. Thanks. You can try the build for now from On Sat, Nov 5, 2016 at 9:49 AM TheRealDannyyy [email protected]
|
General Information:
Problem Description:
When I'm trying to run a packaged Construct 2 game (HTML5) while having "--single-process" set as a property in the chromium-args, NWjs doesn't run properly and immediately closes itself.
Observed Result
NWjs single process starts to run and automatically closes itself after 1-2 seconds without any crash or visible error message.
Expected Result
NWjs should run fine with the recently added single processing argument.
The text was updated successfully, but these errors were encountered: