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

The System Detected an Overrun of a Stack-based Buffer in this application #243630

Closed
codedocpp opened this issue Mar 15, 2025 · 10 comments
Closed
Assignees
Labels
confirmation-pending info-needed Issue requires more information from poster terminal-conpty Integrated terminal issues related to the ConPTY backend

Comments

@codedocpp
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.82.1 1.98.2
  • OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

  1. Start terminal with command prompt (the commandline program must be cmd.exe, if use other program like powershell or git bash this error will not happen).
  2. Run a command like 'cmake --help' to print something.(this step is not necessary but if do this reproduce will be easier)
  3. Input something on this terminal (just input don't run).
  4. Drag the top of the terminal to zoom out it.
  5. A conhost.exe system error message window will pop, the message is "The system detected an overrun of a stack-based buffer in this application.This overrun could potentially allow a malicious user to gain control of this application".

Image

@gjsjohnmurray
Copy link
Contributor

Please update to the current release of VS Code and test again.

@codedocpp
Copy link
Author

Please update to the current release of VS Code and test again.

It's already the lastest version.

@meganrogge
Copy link
Contributor

Pls attach a gif

@meganrogge meganrogge added the info-needed Issue requires more information from poster label Mar 19, 2025
@codedocpp
Copy link
Author

Pls attach a gif
Is it okay like this?

Image

@meganrogge meganrogge added bug Issue identified by VS Code Team member as probable bug confirmation-pending terminal-shell-cmd An issue in the terminal specific to command prompt on Windows and removed info-needed Issue requires more information from poster labels Mar 19, 2025
@Tyriar Tyriar assigned deepak1556 and unassigned meganrogge Mar 20, 2025
@Tyriar Tyriar added terminal-conpty Integrated terminal issues related to the ConPTY backend and removed bug Issue identified by VS Code Team member as probable bug terminal-shell-cmd An issue in the terminal specific to command prompt on Windows labels Mar 20, 2025
@deepak1556
Copy link
Collaborator

Can you run Developer: Open User Data Folder and attach the *.dmp files from the Crashpad folder.

@deepak1556 deepak1556 added the info-needed Issue requires more information from poster label Mar 20, 2025
@codedocpp
Copy link
Author

Can you run Developer: Open User Data Folder and attach the *.dmp files from the Crashpad folder.

I can't find this specified *.dmp file, this Crashpad folder has two empty folders names attachments and reports and two files names metadata and settings.data. Do I need to turn on certain options?

@deepak1556
Copy link
Collaborator

When you run Preferences: Configure Runtime Arguments is "enable-crash-reporter": true ? If you are unable to find existing reports, can you attempt to generate one using the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

@codedocpp
Copy link
Author

When you run Preferences: Configure Runtime Arguments is "enable-crash-reporter": true ? If you are unable to find existing reports, can you attempt to generate one using the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

I do this but the file not generate. Whether the file *.dmp is generated only when the whole program crashes? In this issue only the terminal will crash.

@deepak1556
Copy link
Collaborator

Whether the file *.dmp is generated only when the whole program crashes? In this issue only the terminal will crash.

It will be captured for any process in the application tree, seems like the crash is in system conhost process which the built in crash reporter cannot monitor.

Can you follow the steps from https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps to capture dump files, for the DumpType set it to Full dump (2). Send the files to Deepak.Mohan@microsoft.com instead of attaching to this issue.

Additionally, please check if the issue repros with our insiders https://code.visualstudio.com/insiders

Copy link

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmation-pending info-needed Issue requires more information from poster terminal-conpty Integrated terminal issues related to the ConPTY backend
Projects
None yet
Development

No branches or pull requests

5 participants