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.

Sign up for GitHub

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

Jump to bottom

[Bug] High CPU usage on EventSub WebSocket after reconnect #229

Closed
Xemdo opened this issue Apr 20, 2023 · 0 comments · Fixed by #231
Closed

[Bug] High CPU usage on EventSub WebSocket after reconnect #229

Xemdo opened this issue Apr 20, 2023 · 0 comments · Fixed by #231
Assignees
@Xemdo
Labels
bug Something isn't working

Comments

@Xemdo
Copy link
Contributor

Xemdo commented Apr 20, 2023 •
edited
Loading

What is the problem?

There's high CPU usage on EventSub WebSocket server after reconnect is run. At least one user must be connected during the reconnect for this to happen.

Operating System

All

Architecture Version (x86, x64, arm, etc)

All

Steps to reproduce

  1. twitch event websocket start
  2. Connect to the server
  3. From another terminal window, twitch event websocket reconnect
  4. CPU spikes during correct and stays spiked after

Originally reported by @Awakened-Redstone
@Xemdo Xemdo added the bug Something isn't working label Apr 20, 2023
@Xemdo Xemdo self-assigned this Apr 20, 2023
@Xemdo Xemdo mentioned this issue Apr 20, 2023
Merged
4 tasks
Xemdo added a commit that referenced this issue Apr 21, 2023
@Xemdo
Merge pull request #231 from twitchdev/fix-229
0a65126 
Fix #229
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Xemdo Xemdo

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #229 twitchdev/twitch-cli
1 participant
@Xemdo