[v0.19.2+] --single-process Is Not Working Properly (Running Two Separate Processes)

[TheRealDannyyy]

General Information:

• Using NW.js version 0.19.2 & newer
• Windows 7 with latest drivers
• Package.nw folder including package.json manifest
• Task-Manager screenshot:
  

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, NW.js runs a total of 2 processes instead of the intended single process.

Observed Result
NW.js single process starts to run with two processes using "--single-process" specified inside the package.json manifest.

Expected Result
NW.js should run fine with the single processing argument and always run with a single process.

[rogerwang]

The additional process is used for crash dumping. And it's intended to be a separate process on windows: https://groups.google.com/a/chromium.org/d/msg/chromium-dev/gQ-IMJwedcs/ujos2lVTAAAJ

The other parts runs in the same process as expected.

Does this affect any aspect of you app?

[TheRealDannyyy]

It affects some game recorders that are not able to detect games with multiple processes.

[rogerwang]

Then we can have a workaround with an option to disable crash dumping.

[TheRealDannyyy]

Then we can have a workaround with an option to disable crash dumping.

That would be very much appreciated, thanks a lot!

[TheRealDannyyy]

@GnorTech
Both 32bit and 64bit (nw.js 0.20.1) versions crash when I use "--disable-crash-handler=true" as a command line flag inside a shortcut. I specified "--single-process" inside the manifest and I followed the required steps as mentioned inside the docs.

All I can do is provide the crashlog by Windows (it's in German but you guys will surely figure it out).
Am doing something wrong or is it indeed not working properly?

[rogerwang]

It's fixed again in git and will be available in the next nightly build of 0.20 branch.

[TheRealDannyyy]

It's fixed again in git and will be available in the next nightly build of 0.20 branch.

Thanks again.

[rogerwang]

added tag to track the need for a test case for --disable-crash-handler=true

[TheRealDannyyy]

@rogerwang It works fine in NW.js v0.27.2 and I assume in previous versions as well.

This is off-topic but I'd really appreciate it if you could "merge" this feature with the --single-process arg or make it possible to disable the crash handler from the manifest.