sometimes stall after interrupting long text output

[xuefer]

WSLBridge=0
cat /dev/urandom, # minttydisappear (either crash or exit normally (?) but unexpectedly) at some point

WSLBridge=2
cat /dev/urandom # keep going fine

version 3.8.0.3, windows 10, with conhost.exe replaced by openconsole.exe (1.25.2511.6001)

[mintty]

Not sure what you mean by "crash". For me, with conhost from new openconsole, random output sometimes terminates wsl, sometimes hangs. With the old conhost, after a short while output stops with "cat: write error: Input/output error".
With wslbridge2, it does not happen. With WSLBridge=1, did you install the old wslbridge gateway?

The point is: the same behaviour appears with other terminals, xterm, urxvt. So it is not a mintty issue. It may be worth to report it to the cygwin mailing list. My speculation:
Involved software is Windows wsl.exe, the Windows conhost layer, and the cygwin pty driver. It may be an interworking issue of these or caused by one of them.

Note 1: it is generally not advisable to output random binary stuff to a terminal as this may change all kinds of terminal modes from which you'd need to recover before you can continue to interact normally.
Note 2: the OpenConsole conpty layer seems to enforce strict encoding checking, so byte streams that are not valid UTF-8 may be filtered out or cause undesirable behaviour.

[xuefer]

typo mistake. WSLBridge=1 -> WSLBridge=2

[mintty]

Further analysis: it also happens without cygwin involved: cmd.exe, then wsl, then cat /dev/random. After a while, the console window gets stalled.
So I'd suggest to report this either to the Microsoft WSL project or to the Microsoft Terminal project (which OpenConsole is part of).
Marking invalid here. Further insights appreciated.

[xuefer]

I'm using 1.25.2511.6001 as conhost.exe, windows 10. there's still difference
with cmd then wsl /bin/bash, cat /dev/random | xxd -> no stall, then ctrl+c -> no stall
with wsltty then , cat /dev/random | xxd -> no stall, wait (or more seconds like 10s then ctrl+c -> freeze

[mintty]

This time I can reproduce a difference. I'll investigate.

I'm using 1.25.2511.6001 as conhost.exe

That is, openconsole from Windows terminal as conhost, right?
Using 1.25.10421.0 here, the latest pre-release published as "Canary".

[mintty]

Well, I could reproduce it in Windows 10 but not in Windows 11.
All attempts to analyse the issue make it disappear, it's a Heisenbug.