You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some Windows 7 hosts we see the following error printed in the console window if cmd.exe is run under control of winpty-agent.exe: Not enough storage is available to process this command.
It is unclear why this happens on some hosts and not on others, but we found that it is caused by setting the console title to an empty string. The error is just cosmetic, though, there is no functional impact, AFAICT.
On hosts where this happens, it can also be reproduced independent of winpty by running a batch script using the start command with an empty title string: start "" /w script.bat
The suggested fix/workaround is to set the initial console title to e.g. a single space instead.
The text was updated successfully, but these errors were encountered:
I've seen that error before but never figured out the cause. It always reproduced for me when I invoked winpty from a Cygwin SSH connection. I just tried it again, and setting the title to a single space fixes the problem. A single space seems reasonable enough. I'll have this fixed fairly soon. Thanks for figuring it out!
I wonder if this problem reproduces on other OSs. I noticed some problems with the GetConsoleTitle API in different Windows versions, so maybe that's related.
On some Windows 7 hosts we see the following error printed in the console window if cmd.exe is run under control of winpty-agent.exe:
Not enough storage is available to process this command.
It is unclear why this happens on some hosts and not on others, but we found that it is caused by setting the console title to an empty string. The error is just cosmetic, though, there is no functional impact, AFAICT.
On hosts where this happens, it can also be reproduced independent of winpty by running a batch script using the start command with an empty title string:
start "" /w script.bat
The suggested fix/workaround is to set the initial console title to e.g. a single space instead.
The text was updated successfully, but these errors were encountered: