Stefan Haller 0e3d3d3182 Don't run end-of-input handling for a render that was stopped ... When a task is stopped to make way for a newer one, stopping closes opts.Stop, and the scanner goroutine then closes lineChan. The read loop's select between those two channels is therefore non-deterministic: it can land on the closed lineChan (ok == false) instead of the opts.Stop case, sending a stopped task into the end-of-input branch. There it runs the full finalize — swapping its half-read off-screen buffer in, applying the saved scroll, clamping the origin to the truncated content, and clearing the loading flag — all of which corrupt what the incoming task is about to render. The most visible symptom is a brief frame of truncated content with the scroll yanked to the top, seen when re-renders overlap rapidly (e.g. the periodic background refresh re-rendering a main view faster than it can load, very easy to hit under LAZYGIT_SLOW_RENDER). The underlying bug predates the off-screen render (the EOF branch always clamped the origin via onEndOfInput), but that change made it far worse by also swapping a truncated buffer into the display. Fix it at the source: in the EOF branch, check whether we were stopped and, if so, bail out like the explicit stop case, leaving the view entirely to the task that replaces us. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-08-08 12:58:59 +02:00
..
async_handler.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
async_handler_test.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
tasks.go	Don't run end-of-input handling for a render that was stopped	2026-08-08 12:58:59 +02:00
tasks_test.go	Render async content into an off-screen buffer and swap it in	2026-08-08 12:58:59 +02:00