December 06, 2021, 01:38:25 PM
Welcome, Guest. Please login or register
News: Join us for a FREE Webinar this Thursday at

MediaSignage support forum

Author Topic: nwjs processes not being exited/killed  (Read 2813 times)


  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
nwjs processes not being exited/killed
« on: February 17, 2020, 09:42:13 PM »
I have an issue when a user in Signage Studio updates via Save/Upload. Signage Player is closing some but not all of the nwjs processes. This is also the behaviour when a user stops and quits signageplayer, about three or four nwjs processes remain and continue to eat up memory and sometimes CPU. After several updates there can be in studio, it can bring the system to a grind.

Is there some code I can insert to better manage the child processes? I can't keep telling my clients to manually kill the processes.


  • Administrator
  • Hero Member
  • *****
  • Posts: 5137
  • Karma: +35/-8
    • View Profile
Re: nwjs processes not being exited/killed
« Reply #1 on: February 18, 2020, 03:38:36 AM »
are you using the browser or webkit component? and are you using windows as your player?

one way to kill processes is to use TASKKILL command.  at the end of the timeline, add an external app component - in AppName, specify C:\WINDOWS\System32\taskkill.exe then in Command Line, specify /IM NWJS.EXE.

best regards



Carbonate design by Bloc
variant: carbon
SMF 2.0.12 | SMF © 2016, Simple Machines