Missing output parts when cat'ing UTF-8 stress test #4389

Open
opened 2026-01-30 23:45:47 +00:00 by claunia · 0 comments
Owner

Originally created by @egmontkob on GitHub (Oct 10, 2019).

Environment

Windows build number: Win32NT 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2762.0

Steps to reproduce

ssh to a Linux box.

Get Markus Kuhn's UTF-8 decoder capability and stress test file.

cat UTF-8-test.txt

Expected behavior

Consistent output (which, by the way, reasonably closely matches what's described in the file), regardless of timing, including with various parameters to slowcat.

Actual behavior

Faulty and inconsistent output, presumably depending on the timing of events.

Often the output terminates way too prematurely, e.g. during the intro or section 1 or 2 of the file. Sometimes the succeeding shell prompt isn't printed either, although the shell is already ready to accept a new command.

Other times the output ends as the end of the text file, but as you scroll back you'll notice that a big chunk is missing.

Originally created by @egmontkob on GitHub (Oct 10, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Win32NT 10.0.18362.0 Windows Terminal version (if applicable): 0.5.2762.0 ``` # Steps to reproduce `ssh` to a Linux box. Get Markus Kuhn's [UTF-8 decoder capability and stress test](https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt) file. `cat UTF-8-test.txt` # Expected behavior Consistent output (which, by the way, reasonably closely matches what's described in the file), regardless of timing, including with various parameters to [slowcat](https://gitlab.gnome.org/GNOME/vte/blob/0.58.1/src/slowcat.c). # Actual behavior Faulty and inconsistent output, presumably depending on the timing of events. Often the output terminates way too prematurely, e.g. during the intro or section 1 or 2 of the file. Sometimes the succeeding shell prompt isn't printed either, although the shell is already ready to accept a new command. Other times the output ends as the end of the text file, but as you scroll back you'll notice that a big chunk is missing.
claunia added the Area-OutputIssue-BugNeeds-Tag-FixProduct-Terminal labels 2026-01-30 23:45:48 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4389