starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

on-screen lines randomly disappear after scrolling or missing from the beginning #12637

New Issue
Closed
opened 2026-01-31 03:20:52 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 03:20:52 +00:00
Owner
Copy Link

Originally created by @shivtorov on GitHub (Feb 18, 2021).

Environment

Windows build number:

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0

Windows Terminal 
Version: 1.5.10411.0

Steps to reproduce

I don't know how to reproduce bug.
Just run powershell code, switch between apps, scroll terminal window

Expected behavior

do not lose on-screen lines

Actual behavior

Every day once or twice a day I see lines disappear from Windows Powershell windows.
(I don't use other shells so don't know if the bug is specific to powershell tabs)

examples:

  1. sometimes one line of the output is missing from the beginning.
    I usually notice it when the 1st (header) line is missing in powershell output produced by "format-table".
    If I re-run the PowerShell command, it outputs header line correctly

  2. sometimes initial output of a command is fine, but after scrolling up and down, I notice a line might disappear.
    The screenshot below shows such a case - missing line in the output.
    It is very clear that one line is gone here - because it was the only row in this table.
    Just to clarify - the line was there on the screen earlier. It is disappeared after scrolling up and down

line-disappeared-after-scrolling

Originally created by @shivtorov on GitHub (Feb 18, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0 Windows Terminal Version: 1.5.10411.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> I don't know how to reproduce bug. Just run powershell code, switch between apps, scroll terminal window # Expected behavior do not lose on-screen lines <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Every day once or twice a day I see lines disappear from Windows Powershell windows. (I don't use other shells so don't know if the bug is specific to powershell tabs) examples: 1) sometimes one line of the output is missing from the beginning. I usually notice it when the 1st (header) line is missing in powershell output produced by "format-table". If I re-run the PowerShell command, it outputs header line correctly 2) sometimes initial output of a command is fine, but after scrolling up and down, I notice a line might disappear. The screenshot below shows such a case - missing line in the output. It is very clear that one line is gone here - because it was the only row in this table. Just to clarify - the line was there on the screen earlier. It is disappeared after scrolling up and down ![line-disappeared-after-scrolling](https://user-images.githubusercontent.com/31003608/108339453-8e361000-722b-11eb-8aae-51b85a0f4b34.PNG) <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:20:52 +00:00
claunia commented 2026-01-31 03:20:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 18, 2021):

This happens because PowerShell's line editing library (PSReadline) manually implemented display scrolling by telling the terminal to "shift the contents of the screen up by one, deleting any lines above". This worked with the Windows Console (because of how it was implemented), but does not work properly with Terminal. They have fixed it. If you update the PSReadline module, you will not see this bug any more.

@DHowett commented on GitHub (Feb 18, 2021): This happens because PowerShell's line editing library (PSReadline) manually implemented display scrolling by telling the terminal to "shift the contents of the screen up by one, deleting any lines above". This worked with the Windows Console (because of how it was implemented), but does not work properly with Terminal. They have fixed it. If you update the PSReadline module, you will not see this bug any more.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12637
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?