Tab exits with code 1 when Console.SetBufferSize has been modified and you maximize window

[ajkennedy-HEC]

Possibly related to #1461. I understand the text rendering errors, but the process exiting is different.

When I set the console buffer size to maximum height and run my code from Windows Terminal (in non-maximized, 'windowed' mode), everything appears to work correctly. Windows Terminal honors the buffer-size that I've set, and I can scroll back in history appropriately.

If I maximize that window after running the program, the tab process exits with code 1.

A small C# program that reproduces this issue:

    static void Main(string[] args)
    {
      Console.SetBufferSize(Console.BufferWidth, 32766);
      Console.WriteLine("Buffer size changed.");

      // 100 lines is roughly the minimum it takes to crash the tab. Small behavior changes
      // depending on my initial window size. 
      for (int i = 0; i < 100; i++)
      {
        Console.WriteLine("Line");
      }
    }

Windows Version 2004, OS Build 19041.450
Windows Terminal Version 1.2.2381.0

[DHowett]

Alright, there's gonna be two fixes here: rejecting making the buffer taller than the viewport (sorry, but we've got to do that -- it'll also fix #4062) and fixing the openconsole/conpty crash.

[flevi29]

Oh, that's sad, but understandable. Changing buffer size also causes some weird behavior, where if I resize Windows Terminal a few times the text kinda corrupts.

[DHowett]

Indeed, that’s why we will have to reject buffer size changes 😄