13 comments (13 comments)0 reactions (0 reactions)0 assignees (0 assignees)JavaScript17,294 stars (17,294 stars)2,559 forks (2,559 forks)batch import
help wanted
Description
这是我路由器上的截图
Contributor guide
- Tech stack
- javascriptnodejs
- Domain
- backendperformance
- Issue type
- bug
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 4
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 3-5 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- Node.jsBasic knowledge of memory profiling
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 20
- Research direction
- Reproduce the memory leak by running the proxy under load and monitoring memory usage. Use Node.js heap snapshots (e.g., with inspect) to identify objects that are not garbage collected. Check for event listeners or timers that are not cleaned up, especially in the proxy's HTTP handling code. Review the repository's issue #363 for any additional comments that may provide clues.