Skip to content

Clear writable sockets after the first event #903

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

Closed
wants to merge 1 commit into from

Conversation

mhariri
Copy link

@mhariri mhariri commented Mar 10, 2017

This fixes #807

@mnaberez
Copy link
Member

@jaredsuttles @mhariri This patch #903 and #875 both try to fix the 100% CPU usage issue reported in #807, but they are completely different patches. Can you please have a discussion on why you think one approach or the other should be used, and see if you can come to a consensus on the best way to fix #807? Thanks both for your help.

@mnaberez mnaberez mentioned this pull request Mar 10, 2017
@mhariri
Copy link
Author

mhariri commented Mar 11, 2017

Closing in favour of #875

@mhariri mhariri closed this Mar 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

100% CPU usage (maybe caused by new poll implementation?) (help wanted)
2 participants