Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAIL_FAST crash in conhost after shrinking the buffer height #14328

Open
j4james opened this issue Nov 3, 2022 · 3 comments
Open

FAIL_FAST crash in conhost after shrinking the buffer height #14328

j4james opened this issue Nov 3, 2022 · 3 comments
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Conhost For issues in the Console codebase Severity-Crash Crashes are real bad news.
Milestone

Comments

@j4james
Copy link
Collaborator

j4james commented Nov 3, 2022

Windows Terminal version

Commit cfdea71

Windows build number

10.0.19044.2006

Other Software

No response

Steps to reproduce

  1. Open a cmd shell in conhost.
  2. Open the console Properties dialog.
  3. On the Layout tab, set the Screen Buffer height to 50, and the Window height to 24.
  4. Also make sure the Wrap text output on resize option is UNCHECKED.
  5. Back in the shell, keep pressing enter until you've filled up all 50 lines of the buffer.
  6. Open the Properties again, and set the Screen Buffer height to 24.
  7. Back in the shell, type any letter.

Expected Behavior

I'd expect to see the letter that I typed being output at the prompt.

Actual Behavior

The console crashes with the FAIL_FAST check here:

FAIL_FAST_IF(!(coordCursor.Y == bufferSize.Y));

@j4james j4james added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 3, 2022
@j4james
Copy link
Collaborator Author

j4james commented Nov 3, 2022

I thought at first this was a regression, but once I realised that step 4 was necessary, I was able to reproduce this in my inbox conhost as well. So if it is a regression, it's at least not a very recent one.

@lhecker lhecker added Product-Conhost For issues in the Console codebase Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Priority-2 A description (P2) labels Nov 3, 2022
@carlos-zamora carlos-zamora added Severity-Crash Crashes are real bad news. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 3, 2022
@carlos-zamora carlos-zamora added this to the Terminal v1.17 milestone Nov 3, 2022
@BDisp
Copy link

BDisp commented Jan 3, 2023

This is also happening on conhost by using the System.Console on a C# project and resizing the console height by mouse to zero it will crash with a pipe not connected error. I don't know if it's possible to restore the console on the catch exception handler.

@lhecker
Copy link
Member

lhecker commented Apr 12, 2023

Related to #14298.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Conhost For issues in the Console codebase Severity-Crash Crashes are real bad news.
Projects
None yet
Development

No branches or pull requests

4 participants