-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Find memory leak #1
Comments
see tom-draper/api-analytics#53 issue is with |
JasonLovesDoggo
added a commit
that referenced
this issue
Mar 2, 2025
- Implemented proper cleanup of client connections in the SSE handler to prevent goroutine leaks. - Added buffered channels to the ValueEventServer to prevent blocking and improve concurrency handling. - Improved client disconnection handling in the SSE route to ensure prompt cleanup of disconnected clients. - Added explicit timeout mechanisms in tests to avoid indefinite hanging. - Updated test script to include a mix of connection types (quick, lingering, and zombie) to simulate real-world scenarios. - Updated documentation and added test results. - Bumped version to 1.4.0. Fixes GHSA-vh64-54px-qgf8 potential fix for #1
Looks like GHSA-vh64-54px-qgf8 Was the root caused. Will wait 1 more week to confirm it was the root cause |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systems reach 512mb of memory after ~1w of operation, check stats modules to ensure no leaks.
there seems to be one somewhere
The text was updated successfully, but these errors were encountered: