We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent create NamedPipeClient instance to Connect Server can cause memory leak Task.Factory.StartNew(() => { while (true) { i++; NamedPipeClient<string> _client2 = new NamedPipeClient<string>(Constants.PIPE_NAME); _client2.ServerMessage += OnServerMessage; _client2.Disconnected += OnDisconnected; _client2.Start(); _client2.PushMessage("this is the " + i + "client"); _client2.Stop(); _client2.ServerMessage -= OnServerMessage; _client2.Disconnected -= OnDisconnected; Thread.Sleep(200); } });
Task.Factory.StartNew(() => { while (true) { i++; NamedPipeClient<string> _client2 = new NamedPipeClient<string>(Constants.PIPE_NAME); _client2.ServerMessage += OnServerMessage; _client2.Disconnected += OnDisconnected; _client2.Start(); _client2.PushMessage("this is the " + i + "client"); _client2.Stop(); _client2.ServerMessage -= OnServerMessage; _client2.Disconnected -= OnDisconnected; Thread.Sleep(200); } });
The text was updated successfully, but these errors were encountered:
Is the memory leak on the server or the client side?
Sorry, something went wrong.
No branches or pull requests
Frequent create NamedPipeClient instance to Connect Server can cause memory leak
Task.Factory.StartNew(() => { while (true) { i++; NamedPipeClient<string> _client2 = new NamedPipeClient<string>(Constants.PIPE_NAME); _client2.ServerMessage += OnServerMessage; _client2.Disconnected += OnDisconnected; _client2.Start(); _client2.PushMessage("this is the " + i + "client"); _client2.Stop(); _client2.ServerMessage -= OnServerMessage; _client2.Disconnected -= OnDisconnected; Thread.Sleep(200); } });
The text was updated successfully, but these errors were encountered: