Here's what I found while triaging this issue:

PR #10032 is already linked from the issue and appears to target this startup/memory optimization directly.

Maintainer details

I concluded that tracking issue #10073 is an enhancement/performance item for deferring restored AI conversation CodeDiffView editor creation, with PR #10032 already implementing the lazy-materialization path..

Triage summary

This is an internally-authored tracking issue for PR #10032, which defers CodeDiffView editor creation for restored AI conversations to reduce startup/memory overhead. Code inspection confirms the current restore flow eagerly converts restored file edits into FileDiffs and calls set_candidate_diffs, which creates a CodeEditorView plus InlineDiffView per restored file before the user interacts with the collapsed diff.

Reproducibility

High for restored AI conversations that contain requested file edits. AIBlock::new replays complete restored output, and AIBlock::set_restored_file_edits then populates the restored diff view through the eager CodeDiffView::set_candidate_diffs path.

Likely root cause

AIBlock::set_restored_file_edits currently materializes restored diffs before setting the terminal accepted/rejected/reverted state. CodeDiffView::set_candidate_diffs allocates the editor, diff viewer, subscriptions, and buffers for every file; for completed restored actions those views are usually collapsed/read-only until expansion, so this upfront allocation is avoidable.

Duplicate check

Checked all open non-PR issues and recently closed issues. #10072 is closely related but appears to be a separate PR tracking issue, and no second likely duplicate was found, so this should not be marked as a duplicate.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Defer CodeDiffView editor creation for restored AI conversations #10073

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions