NWJS not completely closing when exiting app

Bugs will be moved here once resolved.

Post » Sat Jan 09, 2016 6:03 pm

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.
B
43
S
12
G
14
Posts: 488
Reputation: 10,570

Post » Mon Jan 11, 2016 7:10 pm

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)
Scirra Founder
B
397
S
236
G
88
Posts: 24,408
Reputation: 194,506

Post » Mon Jan 11, 2016 8:12 pm

Does this happen if you export and run NW.js without Steam client?
A big fan of JavaScript.
B
74
S
20
G
71
Posts: 2,228
Reputation: 44,888

Post » Mon Jan 11, 2016 8:46 pm

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.
B
65
S
22
G
4
Posts: 358
Reputation: 6,555

Post » Mon Jan 11, 2016 11:44 pm

@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.
B
43
S
12
G
14
Posts: 488
Reputation: 10,570

Post » Tue Jan 12, 2016 12:19 am

@FraktalZero - please provide a minimal repro if you can - see the FAQ for info on how to get there if you can't reproduce in a new project.
Scirra Founder
B
397
S
236
G
88
Posts: 24,408
Reputation: 194,506

Post » Tue Jan 12, 2016 1:42 am

@Ashley, I posted it here in this thread, sorry if it wasn't in the bug sections, my bad.
At almost the bottom of the page.

https://www.scirra.com/forum/viewtopic.php?t=166653
B
43
S
12
G
14
Posts: 488
Reputation: 10,570

Post » Wed Jan 13, 2016 5:04 pm

It happens to my project as well, but it's inconsistent.

Sometimes after closing my project, running r220 on nw.js 0.13 beta 2, there is a left over process that uses about 270mb of ram. This is kind of a major issue for me, as it causes steam to think the game is still running, and cannot be opened again until the process has been ended.

I'm going to roll back to alpha 7 to see if the issue persists.
B
37
S
5
G
1
Posts: 155
Reputation: 2,140

Post » Wed Jan 13, 2016 9:52 pm

Me too, my PC started to work slow and when i checked... more than 30 nw.exe in the admin tasks on WIn7, and i have 16gb of ram so imagine :P

SO = Win7
C2 Version: Construct 2 r220
NW.js Version: v0.13.0 beta 3 (Chromium 47) [Requires r217+] - 13th January 2016

Bought from the Scirra webpage no Steam.

To reproduce it is simple, I press F4 to execute the project using NW.js and then i press ESC to exit using an event for it using the BROWSER->Close. SO every time i made this action a nw.exe is created and after close the app the nw.exe i still running.
B
24
S
10
G
3
Posts: 553
Reputation: 4,483

Post » Thu Jan 14, 2016 1:10 am

Same here in preview mode on 2 different computers with the same setup.
Win7
R220 and NW.js 0.13.0 beta 2.

Strangely, no issue on the exported version.
B
72
S
21
G
12
Posts: 314
Reputation: 12,111

PreviousNext

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 3 guests