Feedback from #feedback-app:

"Beachball that looks code review related. It's on a WarpDev from the 14th though, so may not still be an issue"

Attachment included a process sample (warpdev-2026-04-17.txt) showing:

• Physical footprint around 9.2GB
• Main-thread call graph with heavy code_review_view / local code editor activity

Slack message: https://warpdev.slack.com/archives/C08KTPNQN65/p1776430806119909

What needs to be done:

• Investigate potential code-review/local editor path causing beachball and high memory usage.
• Determine whether this reproduces on current WarpDev builds and isolate regression window if fixed.
• Capture mitigation or fix plan if reproducible.

Linear: APP-4119