[Solved] NWJS Not Completely Closing In Preview Mode

Bugs will be moved here once resolved.

Post » Thu Apr 28, 2016 11:50 am

Problem Description
NW.js is still leaving a process behind when using it in C2 Preview mode.
Manually shutting down the process is required.

Attach a Capx
Click HERE!

Steps to Reproduce Bug
  • Open the project
  • Preview using NW.js several times (Change between debug and normal preview from time to time.)
  • Always close the project using the windows "X" symbol

Observed Result
Eventually NW.js will leave a process behind, if unnoticed these processes will eat up a lot of memory.

Expected Result
NW.js should close either way and not just when exported.
Also note that the browser close action is working fine as a temporally workaround event. (eg. On ESC pressed > Close Browser).

Affected Browsers
  • NW.js: (YES)

Operating System and Service Pack
Windows 7 with latest updates and up to date drivers.

Construct 2 Version ID
Newest release r227 Steam release. [Personal Edition]

Additional maybe useful information:
  • NW.js version: v0.14.0
  • Checked C2 data with the Steam software data check system (0 Errors Found)
Last edited by TheRealDannyyy on Thu May 26, 2016 12:56 pm, edited 2 times in total.
ImageImageImage
B
60
S
22
G
78
Posts: 646
Reputation: 44,730

Post » Wed May 04, 2016 12:37 pm

Can't reproduce: previewed 10 times alternating preview and debug and it worked fine.

Besides it would be a NW.js issue if it left behind a process, the C2 engine doesn't control that and I doubt there is anything we can change in our code to influence that. It's probably better to head straight to the NWjs bug tracker for this kind of issue.
Scirra Founder
B
395
S
231
G
88
Posts: 24,367
Reputation: 193,694

Post » Wed May 04, 2016 2:57 pm

Ashley wrote:Can't reproduce: previewed 10 times alternating preview and debug and it worked fine.

Besides it would be a NW.js issue if it left behind a process, the C2 engine doesn't control that and I doubt there is anything we can change in our code to influence that. It's probably better to head straight to the NWjs bug tracker for this kind of issue.

That is weird, so I am the only one with this issue? :|

I guess I'll wait for the next release and see if they fixed it else I'll have to report it there, thanks for you response.
It might be worth mentioning that I switched from desktop (NW.js) to mobile (FF) preview from time to time too.
ImageImageImage
B
60
S
22
G
78
Posts: 646
Reputation: 44,730

Post » Thu May 26, 2016 12:55 pm

This is no longer occurring using v0.14.5 of NWjs.

I don't understand how it fixed itself but perhaps the NWjs devs. secretly updated that part?
Anyway, this can be closed for now.
ImageImageImage
B
60
S
22
G
78
Posts: 646
Reputation: 44,730

Post » Wed Jun 08, 2016 2:16 pm

Hi! I have the same problem. Nwjs is not closing and slowing my computer after launching several times if not to close it every time through CTR/ALT/DEL.
Configuration of PC: Windows 10, Pentium E5200, 4000 RAM. I am using latest version of nwjs.
B
9
S
1
Posts: 16
Reputation: 607

Post » Wed Jun 08, 2016 2:28 pm

Vladimir wrote:Hi! I have the same problem. Nwjs is not closing and slowing my computer after launching several times if not to close it every time through CTR/ALT/DEL.
Configuration of PC: Windows 10, Pentium E5200, 4000 RAM. I am using latest version of nwjs.

@Vladimir

This is a closed and solved bug report and as the 'sticky' says, you should not post in this section.

If you think you have found a bug, please make a new bug report ensuring you follow all of the Bug Reporting Requirements.
If your vision so exceeds your ability, then look to something closer.
Moderator
B
134
S
30
G
84
Posts: 5,375
Reputation: 58,432


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 3 guests