Skip to content
New issue

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

High CPU Usage #4

Open
thaxy opened this issue May 12, 2015 · 4 comments
Open

High CPU Usage #4

thaxy opened this issue May 12, 2015 · 4 comments

Comments

@thaxy
Copy link

thaxy commented May 12, 2015

Hi,

I have a client in a WindowsService which does the following:

var client = new NamedPipeClient<string>("my-pipe");
client.Start();

The UI application acts as the server:

var server = new NamedPipeServer<string>("my-pipe");
server.ClientMessage += OnClientMessage;
server.Start();

Problem:
If my UI application is closed the CPU Usage goes up to 100% on one core.
I guess this is due a missing sleep where the client tries to connect to the server.

Greetings thaxy

Edit:
This Issue was fixed with this reliablehosting@f7267a4 commit in this pull request #3 I hope that acdvorak will update this with his own code. His syntax and knowledge is awesome.

@davidgrupp
Copy link

@thaxy Maybe email @acdvorak about this issue since he has been mia on the project for so long. His email is in his profile.

@thaxy
Copy link
Author

thaxy commented May 20, 2015

@davidgrupp thanks for the reply. But I guess @acdvorak already seen this issue and is too busy with other projects/work. I will let this Issue open, maybe he finds the time in the future.

@davidgrupp
Copy link

@thaxy well if you (or anyone else) needs the change it looks like https://github.com/reliablehosting/named-pipe-wrapper has the fix applied (they also created the PR). You can just clone that repo and compile from source to get a working build. Best of luck!

@thaxy
Copy link
Author

thaxy commented May 21, 2015

You just confirmed what I wrote in my edited original post. But I'm fine with that if this makes it clearer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants