Author Topic: zombie cmd processes  (Read 1184 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1759
  • Hero Points: 172
  • Text
zombie cmd processes
« on: July 21, 2016, 06:02:56 pm »
V21 is leaking hidden cmd windows.
I don't know what does it, but I've got three on my system right now.


Started 7/18/2016
ntpinit.exe   ntpinit.exe   0.01   3,176 K   5,264 K   8672   "C:\Program Files\SlickEdit Pro 21.0.0 Beta1\win\ntpinit.exe" \\.\Pipe\slick\6384.0 \\.\Pipe\slick\6384.1 C:\Windows\system32\cmd.exe

Started 7/20 10:09am
ntpinit.exentpinit.exe0.013,160 K5,280 K8912"C:\Program Files\SlickEdit Pro 21.0.0 Beta1\win\ntpinit.exe" \\.\Pipe\slick\6316.0 \\.\Pipe\slick\6316.1 C:\Windows\system32\cmd.exe

Started 7/20 3:37 pm
ntpinit.exe   ntpinit.exe   0.01   3,172 K   5,576 K   560   "C:\Program Files\SlickEdit Pro 21.0.0 Beta1\win\ntpinit.exe" \\.\Pipe\slick\8124.0 \\.\Pipe\slick\8124.1 C:\Windows\system32\cmd.exe


Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4743
  • Hero Points: 383
Re: zombie cmd processes
« Reply #1 on: July 21, 2016, 06:11:33 pm »
If SlickEdit crashes, you will be left with ntpinit.exe.

jporkkahtc

  • Senior Community Member
  • Posts: 1759
  • Hero Points: 172
  • Text
Re: zombie cmd processes
« Reply #2 on: July 21, 2016, 06:23:21 pm »
I never noticed this with V20.
I don't think V21 has crashed on me, but I have killed it a few times.



A windows JobObject is easy to setup and would ensure this cannot happen.
(A windows JobObject could also be used to make Build->StopBuild work - even with msbuild. msbuild can intentionally ignore ctrl+c for some dumb reason).