From 2dfcc676a13140425cb07120fe8e9efdcda25ea8 Mon Sep 17 00:00:00 2001
From: Neil <4138956+nwparker@users.noreply.github.com>
Date: Sat, 1 Aug 2026 07:38:36 -0700
Subject: [PATCH] docs(crash): use the measured 2.5x in the pane census comment

The JSDoc still carried 3.2x, which was the figure from a bench against a
hypothetical count-only walk with no call and no returned object. Against
the code as shipped it is 2.5x at 200 panes (1.4x at 8, 2.3x at 50, 2.3x
at 1000). The commit message and PR body were corrected; this comment was
missed, and a wrong number in the source outlives the one in the log.
---
 src/renderer/src/lib/pane-manager/pane-manager.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/renderer/src/lib/pane-manager/pane-manager.ts b/src/renderer/src/lib/pane-manager/pane-manager.ts
index 3a34916313c..a4e2574b466 100644
--- a/src/renderer/src/lib/pane-manager/pane-manager.ts
+++ b/src/renderer/src/lib/pane-manager/pane-manager.ts
@@ -219,7 +219,7 @@ export class PaneManager {
   }
 
   /** Why separate from getPanes: same crash-path reason as getPaneCount —
-   *  measured 3.2x cheaper at 200 panes than materializing a view per pane. */
+   *  measured 2.5x cheaper at 200 panes than materializing a view per pane. */
   getPaneBufferCensus(): TerminalBufferCensus {
     return sumTerminalBufferSizes(this.panes.values())
   }