NWJS not completely closing when exiting app

Bugs will be moved here once resolved.

Post » Wed Mar 09, 2016 1:15 am

Is the nwjs team even aware of the problem yet?
B
143
S
72
G
19
Posts: 1,777
Reputation: 21,704

Post » Wed Mar 09, 2016 4:48 am

alspal wrote:Is the nwjs team even aware of the problem yet?


I don't think so. We could report the issue here:
https://github.com/nwjs/nw.js/issues

But if the gui.App.quit(); command works properly, which it seems to, then it seems this would be something to fix in Construct rather than in NW.JS.
FREEDOM: Diegesis - Out Now for Windows! http://freedom.quicksandgames.com
B
21
S
5
G
1
Posts: 83
Reputation: 1,793

Post » Wed Mar 09, 2016 6:11 am

I have observed this as well with my Non-Steam copy and Non-Steam game. I am running x64 Windows 10 and my task manager is populated with a ton of these after testing in NWJS. They do take up a small amount of memory (for my project around 30-60mb), so it may be a problem for low end users.
B
8
S
1
G
1
Posts: 19
Reputation: 1,093

Post » Wed Mar 09, 2016 8:52 am

Is this a Windows 10 problem? I have after uninstall an reinstall NWjs4c2 no problems with nw-tasks after exit a nw program under windows 7.
B
24
S
3
G
1
Posts: 444
Reputation: 2,151

Post » Wed Mar 09, 2016 7:15 pm

EDIT- Ok I worked on this issue a little more with the help of a programmer friend and we figured out a better possible solution.

1. Find your exported project's package.nw file and open it (it can be opened as a zip).

2. Open up the index.html file inside that archive.

3. Paste this code right before the last closing </script> tag:

var win = window['nwgui'].Window.get();

win.on('close', function () {
window['nwgui'].App.quit();
});

4. Save the new index.html file and the changed package.nw.

5. Test out your game to see if all processes close fully upon exit.
FREEDOM: Diegesis - Out Now for Windows! http://freedom.quicksandgames.com
B
21
S
5
G
1
Posts: 83
Reputation: 1,793

Post » Thu Mar 17, 2016 2:31 pm

@Quicksand It seems to work for me! Thanx for the workaround. :)
B
69
S
21
G
12
Posts: 314
Reputation: 12,036

Post » Tue Mar 22, 2016 3:31 pm

I've incorporated that workaround for the next beta. That should paper over the cracks for existing projects, and new projects should not be affected anyway, since I think this stemmed from upgrading a NW.js 0.12 app. Closing.
Scirra Founder
B
386
S
229
G
87
Posts: 24,207
Reputation: 191,602

Post » Wed Mar 23, 2016 3:00 pm

Ashley wrote:I've incorporated that workaround for the next beta. That should paper over the cracks for existing projects, and new projects should not be affected anyway, since I think this stemmed from upgrading a NW.js 0.12 app. Closing.


Confirmed.
Fixed in r255.
No ghost processes in a project that previously had them.
Image ImageImage
B
167
S
50
G
160
Posts: 8,168
Reputation: 103,432

Post » Wed Mar 23, 2016 3:30 pm

@newt - A new typo *r225. XD
Image



The Things you can create is only limited by your imagination. If you don't have the skills then use your motivation as a natural force to exceed all expectations. Chadori RebornXD
B
55
S
17
G
90
Posts: 1,111
Reputation: 59,145

Post » Wed Mar 23, 2016 4:01 pm

Typo, or wishful thinking.
Image ImageImage
B
167
S
50
G
160
Posts: 8,168
Reputation: 103,432

PreviousNext

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest