[Fedor Losev]

After switching to prerelease stopping an Angular server does not terminate node process and holds the port.

In UI the server is shown as [Stopped] but the process is still running and is holding the port. So starting new server or restart is not possible without killing the node process through task manager.

Note this doesn’t happen always (though almost every stop/start or restart for me) and happen less if no page was served yet.

• This topic was modified 6 years, 10 months ago by Fedor Losev.
• This topic was modified 6 years, 10 months ago by Fedor Losev.

[support-swapna]

Fedor,

We could replicate the issue intermittently at our end. The dev team is looking into it.
Thank you for reporting.

–Swapna
MyEclipse Support

[Fedor Losev]

Hi, any news on this issue? I don’t think it is low priority, it is quite inconvenient and happens frequently during development.

[Brian Fernandes]

Fedor,

Certainly not low priority – we’re targeting this fix for the next release, CI 8. Apologies for the inconvenience caused, I know having to kill Node externally can be quite annoying.

[support-piotr]

Fedor,

This issue seems to have something to do with Windows Creators Update, where child node process (the ng serve) is not killed together with it’s parent sh process. We have added a workaround, which works very good. The only downside is that process might not get killed during first few secs of starting up, when there is no connection to Angular IDE made yet. Please update to prerelease to test it and let us know how well it works for you.

[support-swapna]

Fedor,

Our latest release, 2017 CI 8 is out and it includes the fix for Node.js process termination issue. Please update to 2017 CI 8 and let us know how it works for you.

–Swapna
MyEclipse Support

[Fedor Losev]

Thanks, seems working

[Author]

Posts