NWJS not completely closing when exiting app

Problem Description

I am trying to publish my game on steam. Whenever I launch the game using NWJS everything works fine. It's when I close the app. If I try to play another game, Steam will inform me that the app hasn't completely closed and I am forced to go through the task manager in order to completely close NWJS.

Attach a Capx

I am not sure what type of capx will help show this problem

Description of Capx

N/A

Steps to Reproduce Bug

• Step 1 Open a game in steam using NWJS v0.13.0 beta 2 (Chromium 47)
• Step 2 Try closing the app
• Step 3 etc. Try opening another game or even the same game in steam

Observed Result

https://gyazo.com/78e57edad5b42497c5ed061cfd9dbd02

https://gyazo.com/a310051dc097f2b08919f516cb19ba53

Expected Result

____ What do you expect to happen? ____

Affected Browsers

• Chrome: (YES/NO)
• FireFox: (YES/NO)
• Internet Explorer: (YES/NO)

Operating System and Service Pack

Windows 10

Construct 2 Version ID

r220

Step 2

Try closing the app

Does that happen when closing it with the browser event "close" and/or using the default "X" to close a window?

TheRealDannyyy it happens with both options

when i open the game, these two processes run

https://gyazo.com/98b19c94130477d36021d4894616e4e1

*UPDATE*

Using the browser close option DOES seem to close everything. It's when you press the X button to close the window that it stays running

Just for reference, I just tested using the non-steam version (x64) and it seems OK - no running process left open.

when i open the game, these two processes run

*UPDATE*

Using the browser close option DOES seem to close everything. It's when you press the X button to close the window that it stays running

This seems to be an issue by NW.js and not Construct 2 but anyway Ashley should take a quick look at this just to make sure.

when i open the game, these two processes run

https://gyazo.com/98b19c94130477d36021d4894616e4e1

*UPDATE*

Using the browser close option DOES seem to close everything. It's when you press the X button to close the window that it stays running

I don't think the number of processes running is relevant. When I run an exported NWjs it shows 3 process - they all disappear when I close the game.

Same happens with Kaspersky - usually more than 1 process can be running.

Thanks for your help guys

zenox98 TheRealDannyyy very much appreciated!

I uploaded the latest build to steam and tested the close browser. It works well when its in preview in C2. but when I export and upload to Steam, it never closes on its own regardless of whether or not I close in game or use the X on the window. Hm...

Here's an older forum post about the same issue on another site. Not sure if this applies here, but I wanted to share the information.

https://github.com/nwjs/nw.js/issues/325

Having similar issue. Can't test my project with NW,js viewer. But I can test it with Chrome and Firefox. But I'm having this issue just with my project. If I test a new project I have no issues at all.

I can't reproduce this in either the Steam or standalone versions of C2 when previewing with NW.js: it appears to close down just fine, even with Steam open and running in the background. So if I understand right, this only happens when you've published an app to Steam and are running it from Steam, right? Are you sure you have not configured some special command line parameters or launch options that Steam might be applying and breaking it? Perhaps it's related to the Steam overlay, does it help if you disable that? (It's caused some problems in the past before IIRC)

Does this happen if you export and run NW.js without Steam client?

It happened to me JUST with the NW.js live build released 6 jan 2016. Seems like Roger added this feature as a test and decided to remove it straight away.

Ashley

I'm having this same issue but I'm not using steam. It happens only with my working project. If I create a new project I'm not able to repeat this issue.