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

Unified Diff: Severe performance degradation when editing with folded unchanged regions

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the Unified Diff preference and the folding mechanism described in the report, then profile typing with many unchanged regions folded. Investigate whether annotation recomputation, projection updates, or diff recalculation runs on each document change. Done means normal input responsiveness with many folded regions and coverage for this reproduction scenario.

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

描述

Problem

When the preference "Fold unchanged regions, keeping a few lines of context around each change" is enabled and many unchanged regions are folded, editing the document becomes very slow. User input is barely registered or has a significant delay, making the editor practically unusable in this state.

Steps to Reproduce

  1. Enable Unified Diff in Preferences > Compare/Patch.
  2. Enable "Fold unchanged regions, keeping a few lines of context around each change".
  3. Open a file with many changes so that a large number of unchanged regions are folded.
  4. Start typing / editing in the editor.

Expected Behavior

Editing performance should be unaffected by the number of folded regions. User input should be processed at normal speed regardless of the folding state.

Actual Behavior

The editor becomes very slow. Keystrokes are delayed or dropped, making editing effectively impossible when many regions are folded.

Notes

This issue requires root-cause analysis. The folding mechanism likely triggers expensive recalculations (e.g. annotation recomputation, projection updates, or diff recalculation) on every document change, which does not scale with large numbers of folded regions.

主要语言
Java
星标
165
派生
174
平均合并
2 天 16 小时
30 天内合并 PR
45

环境准备

从这里开始

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

eclipse-platform/eclipse.platform 的其他 Issue

查看 eclipse-platform/eclipse.platform 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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