内存泄露？

Repository metrics

Stars

17,294 stars (17,294 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

Contributor guide

Research direction

Investigate the memory usage by examining the screenshot and reproducing the issue. Use Chrome DevTools or Node.js heap snapshots to identify the leak source. Check for unreleased references, especially in event listeners, timers, or network requests.

Tech stack

javascript

Domain

api

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Needs investigation

Prerequisites

GitJavaScript

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40