*One suspect is the fhandler_console::cons_master_thread (), which attempts to mine signals within the input stream; yet it may not handle a single key being represented by multiple events.*; furthermore one of the few uses of WriteConsoleInput Is there any means of disabling the feature for testing?
Interface details can be under: https://github.com/microsoft/terminal/blob/main/doc/specs/%234999%20-%20Improved%20keyboard%20handling%20in%20Conpty.md On Sat, Aug 31, 2024 at 10:33 AM Takashi Yano <takashi.y...@nifty.ne.jp> wrote: > On Fri, 30 Aug 2024 19:56:34 +0800 > Adamyg Mob wrote: > > Cygwin: CYGWIN_NT-10.0-19045 WEED3 3.5.4-1.x86_64 2024-08-25 16:52 UTC > > x86_64 Cygwin > > Windows Terminal version: 1.20.11781.0 > > Windows build number: 10.0.19045.4780 > > > > When running a cygwin64 based terminal application under a MsTerminal > > session, with win32-raw-mode "\033[?9001h" enabled, > > after brief input in the application becoming unresponsive and the > session > > rapidly consumes all available memory/cpu.. > > > > Test application attached, plus ticket > > https://github.com/microsoft/terminal/issues/17824 contains additional > > information. > > Thanks for the report. > > Are there any documents for win32-raw-mode "\033[?9001h" ? > > I am very puzzled with that WriteConsoleInput() with one event > generates ~15 input events for ReadConsoleInput() in this mode. > > -- > Takashi Yano <takashi.y...@nifty.ne.jp> > -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
