Repository navigation
Description
Describe the bug
When switching away from a workspace that contains a running terminal pane and then coming back, the terminal briefly renders the correct content and then falls into a corrupted visual state.
The key symptom is not just "blank output" or "slow repaint".
The content can appear correctly for a moment, then large black blank regions take over the view. Repeating the workspace switch makes the problem worse: each switch appears to add another ghost/stale terminal layer or another large blank region.
This makes the terminal effectively unreadable.
Expected behavior
Returning to an existing terminal pane after a workspace switch should preserve the visible terminal state exactly, or at minimum repaint into a clean usable state without accumulating artifacts.
Actual behavior
After switching away from a workspace and returning to the same terminal pane:
- the terminal may flash the correct content briefly
- then large black blank regions appear over the terminal
- repeated workspace switches make the corruption worse
- the terminal becomes unreadable because ghost/stale terminal regions accumulate
This does not look like missing PTY output. It looks like a post-attach / post-visibility renderer or restore lifecycle bug.
Reproduction
- Open a workspace with a terminal pane.
- Start a dense TUI workload inside the terminal (for example Codex CLI).
- Switch to another workspace.
- Return to the original workspace.
- Observe a brief correct render followed by black blank regions / stale terminal ghosting.
- Repeat workspace switching a few times.
- Observe that the corruption accumulates and readability gets worse on each switch.
Observed pattern
The strongest signal is this:
- the correct content is visible for a moment
- then a later lifecycle pass corrupts the pane
That suggests the failure is after terminal output arrives.
So this appears to be a render / restore / reattach problem, not a subprocess output problem.
Environment
- Superset Desktop: 1.4.7
- macOS: Apple Silicon
- workload inside terminal: Codex CLI
Related issues
This looks related to the same family, but more severe / more cumulative:
- [bug] when focusing back on terminal, content gets corrupted #3208
- [bug] Codex terminal state corrupts on pane reattach after tab/workspace switch #3309
- [bug] Terminal can still repaint into a stale visual state after focus/workspace restore #3321
The specific difference here is the progressive ghosting / accumulating black regions after repeated workspace switches.
Additional notes
I intentionally omitted private/local environment details and internal workspace names. If a maintainer wants a smaller public repro or wants me to test a candidate patch, I can do that.
Activity
AytuncYildizli commentedon Apr 11, 2026
Additional note after more local repro:
The strongest signal is that the correct terminal content can appear briefly and then get overwritten by large black/stale regions.
So this does not look like "the subprocess never produced output".
It looks more like:
Also, repeated workspace switches make the problem progressively worse, which suggests some kind of cumulative reattach / stale-layer / duplicate-restore behavior rather than a one-off failed repaint.
That is why this feels closer to the same family as:
If helpful, I can test a candidate patch against this exact repro pattern.
fix: solve #3351 — refresh terminal after WebGL renderer swap
Kitenite commentedon Jul 11, 2026
Closing as a duplicate of #5605, the consolidated tracker for stale
terminal-renderingissues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5605 and we'll reopen.