Construct 2 - NW.js Preview Leaves Ghost Processes

  • Problem Description

    It seems like the recent NW.js release leaves ghost processes behind again.

    I could only notice this happening in preview though so I assume that C2 is at fault.

    Attach a Capx

    Download HERE

    Description of Capx

    Random example to make use of NW.js preview.

    Steps to Reproduce Bug

    • Open the example (make sure that NW.js v0.22.0 is installed)
    • Preview in NW.js
    • Notice that it previews just fine
    • Close the preview
    • Start The preview again and notice that it doesn't work
    • You should be able to notice 2 ghost processes

    Observed Result

    NW.js preview seems to have issues when used multiple times.

    It leaves processes behind which seem to hinder all future previewing attempts.

    (Manually closing those processes doesn't fix the issue either, which is very odd.)

    Task manager processes:

    Expected Result

    NW.js previewing should work fine, just like it did in earlier versions of NW.js / C2.

    Affected Browsers

    • NW.js: (YES)
    • Chrome: (NO)
    • FireFox: (NO)
    • Internet Explorer: (NO)

    Operating System and Service Pack

    Win 7 SP1, everything up to date.

    Construct 2 Version ID

    Release 244 (64bit/Steam)

  • With NW.js 0.23.0 I can't reproduce any problem, it always closes fine here.

  • With NW.js 0.23.0 I can't reproduce any problem, it always closes fine here.

    Hmm... might be an issue caused by something on my end. Is there a way to completely "reset" NW.js (e.g. registry values)?

    Please note that this only happens using C2 preview, the exported game runs and closes fine.

  • Alright I finally found the issue and it's caused by the --in-process-gpu chromium arg. Removing that arg fixes all the "ghost process" problems.

    EDIT: I have reported this issue to the NW.js dev's and they have confirmed it: https://github.com/nwjs/nw.js/issues/6059

    This issue is not caused by Construct 2 and therefor can be closed.

  • TheRealDannyyy I removed that line " --in-process-gpu" at the end of my package.json file? (I added in because the Steam4c2 plugin by AJ2DI suggested to add it in.) Hopefully my players will stop having issue now! thanks

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • TheRealDannyyy I removed that line " --in-process-gpu" at the end of my package.json file? (I added in because the Steam4c2 plugin by AJ2DI suggested to add it in.) Hopefully my players will stop having issue now! thanks

    It seems to work without it but it still didn't get 100% confirmed from the Steam4C2 Dev's, some features might not work as intended without it.

    I would be careful with this, especially when you have a game on Steam and plan to update it with this experimental change.

    I'm not liable for any damages caused by this change, everything is at your own risk.

  • This has been fixed quite a while ago: https://github.com/nwjs/nw.js/issues/6059

    @Ashley feel free to close this one.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)