Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bug: memory leak

未关闭
#372 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
frontend

调研方向

Start at the note switching flow and inspect how the active note and its related objects are retained or released. Compare memory snapshots before and after repeatedly switching between two notes, then check again after waiting. Done means previously used objects are reclaimed and memory no longer grows with continued switching.

由索引模型根据 Issue 内容生成。

描述

Summary

When the user switches between notes, previously used objects are not cleared from memory, so the application uses more and more RAM over time, which makes the application increasingly laggy.

How to reproduce

  1. Create 2 notes with content
  2. Take a memory snapshot
  3. Switch between the notes for an extended period of time
  4. Take a second memory snapshot
  5. Wait some time and take another memory snapshot to prove that the objects are not cleared on their own

Screenshot

Image
主要语言
Vue
星标
12
派生
6
平均合并
23 天 16 小时
30 天内合并 PR
1

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codex-team/notes.web 的其他 Issue

查看 codex-team/notes.web 的全部 Issue

相似的 Issue

更多 Web Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。