Share via

OS WINDOWS-10 keeps bound socket active until closing last child created process

Anonymous
2022-10-06T11:01:42+00:00

Hi Guys,

I have a problem, which has been activated not long time ago, I suppose.

The problem is that bound socket is rested active after closing process, if this process created a few children processes after binding socket to any port.

Let's imagine following scenario:

Watchdog app-n binds socket through which it communicates with created children.

After activating the system, i.e. opening all relevant applications a watchdog has been crashed.

User activates Watchdog application once again and pppppppp.......

Socket is already bound to the port

This is a system behavior, which acts like this short time ago. Could you explain why it was done this way or such behavior is unexpected?

Best regards,

Boris

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-10-07T08:33:12+00:00

    Hi Boris Legachov，

    Welcome to Microsoft Community.

    This question is out of scope for the Answers Support Community. The best place to get help for your question is Microsoft Docs, which is intended to support more advanced users such as yourself.

    Here is a link to some general documentation that may be useful, and here is a link to the forum where you can repost your question to resolve the issue. I won’t be able to help

    Thanks for your patience and understanding!

    Best Regards,

    Manson - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments