memory leak
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
- The client is WebSocket of JavaScript.There are 5,000-8,000 connections, and clients often close or break unexpectedly (tabs are closed).WebSocketServer runs for about 2 days, when the memory usage exceeds 1GB, there will be a memory overflow.WebSocketServer USES Secure Connection.
- When the number of connections is not at its peak, memory does not drop, but slowly increases.
- When the number of connections is large, websocketserver.stop can be time-consuming (at least more than 2 minutes).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Secure Connection WebSocketServer workload with 5,000–8,000 connections, unexpected client closures, two days of runtime, memory usage, and stop duration. Compare memory when connections are below peak and record whether the leak and slow stop can be isolated and resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100