starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

conhost crashes when Vim is run via ConEmu #29

New Issue
Closed
opened 2026-01-30 21:40:04 +00:00 by claunia · 14 comments
claunia commented 2026-01-30 21:40:04 +00:00
Owner
Copy Link

Originally created by @bgshacklett on GitHub (Nov 5, 2017).

  • Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.17025.1000]
  • Vim Version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 22 2017 22:02:21)
MS-Windows 64-bit console version
Included patches: 1-1213
Compiled by appveyor@APPVYR-WIN
  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
  1. Open a new ConEmu instance.
  2. Type vim, then press the Enter key

  • What's wrong / what should be happening instead:

    • conhost.exe crashes
    Faulting application name: conhost.exe, version: 10.0.17025.1000, time stamp: 0x9d420209
Faulting module name: ntdll.dll, version: 10.0.17025.1000, time stamp: 0x174af1e9
Exception code: 0xc0000374
Fault offset: 0x00000000000f511b
Faulting process id: 0x28a8
Faulting application start time: 0x01d351c58f135167
Faulting application path: C:\WINDOWS\system32\conhost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ac139509-a65e-4a2d-80a2-2e7a3c48df2b
Faulting package full name: 
Faulting package-relative application ID:
    • Vim continues running until it's terminated.
    • Vim's CPU utilization jumps significantly, pegging the CPU at 100%
    • After Vim is terminated, I get an error stating that PowerShell has stopped working.

  • Other Notes:
    Similar behavior arises when attempting to run NeoVim (nvim.exe) with $env:TERM=xterm-256color

Originally created by @bgshacklett on GitHub (Nov 5, 2017). * Your Windows build number: (Type `ver` at a Windows Command Prompt) ``` Microsoft Windows [Version 10.0.17025.1000] ``` * Vim Version ``` VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 22 2017 22:02:21) MS-Windows 64-bit console version Included patches: 1-1213 Compiled by appveyor@APPVYR-WIN ``` * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) 1. Open a new ConEmu instance. 2. Type `vim`, then press the Enter key * What's wrong / what should be happening instead: * conhost.exe crashes ``` Faulting application name: conhost.exe, version: 10.0.17025.1000, time stamp: 0x9d420209 Faulting module name: ntdll.dll, version: 10.0.17025.1000, time stamp: 0x174af1e9 Exception code: 0xc0000374 Fault offset: 0x00000000000f511b Faulting process id: 0x28a8 Faulting application start time: 0x01d351c58f135167 Faulting application path: C:\WINDOWS\system32\conhost.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ac139509-a65e-4a2d-80a2-2e7a3c48df2b Faulting package full name: Faulting package-relative application ID: ``` * Vim continues running until it's terminated. * Vim's CPU utilization jumps significantly, pegging the CPU at 100% * After Vim is terminated, I get an error stating that PowerShell has stopped working. * Other Notes: Similar behavior arises when attempting to run NeoVim (`nvim.exe`) with $env:TERM=xterm-256color
claunia added the Product-ConhostWork-Item labels 2026-01-30 21:40:04 +00:00
claunia commented 2026-01-30 21:40:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 6, 2017):

Well that looks bad. We haven't pushed out too much code in that insiders build, but that could be our fault.

Filed a bug to investigate more.

@zadjii-msft commented on GitHub (Nov 6, 2017): Well that looks bad. We haven't pushed out too much code in that insiders build, but that could be our fault. Filed a bug to investigate more.
claunia commented 2026-01-30 21:40:05 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 6, 2017):

If there's anything else I can do to help (capturing logs, etc.); I'd be happy to do so.

@bgshacklett commented on GitHub (Nov 6, 2017): If there's anything else I can do to help (capturing logs, etc.); I'd be happy to do so.
claunia commented 2026-01-30 21:40:05 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 7, 2017):

One thing I forgot to mention, I believe it started in the previous build (17017?).

@bgshacklett commented on GitHub (Nov 7, 2017): One thing I forgot to mention, I believe it started in the previous build (17017?).
claunia commented 2026-01-30 21:40:06 +00:00
Author
Owner
Copy Link

@adiviness commented on GitHub (Nov 8, 2017):

Where did you get that version of vim and what version of conemu are you using? this doesn't repro for me with the latest stable versions of those two. my vim says VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 23 2017 19:48:19) (x86 version) and conemu is the x64 version 161206 stable.

@adiviness commented on GitHub (Nov 8, 2017): Where did you get that version of vim and what version of conemu are you using? this doesn't repro for me with the latest stable versions of those two. my vim says `VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 23 2017 19:48:19)` (x86 version) and conemu is the x64 version 161206 stable.
claunia commented 2026-01-30 21:40:06 +00:00
Author
Owner
Copy Link

@adiviness commented on GitHub (Nov 8, 2017):

Also, does this only happen when vim is run through conemu or does it crash when run through the normal console as well?

@adiviness commented on GitHub (Nov 8, 2017): Also, does this only happen when vim is run through conemu or does it crash when run through the normal console as well?
claunia commented 2026-01-30 21:40:06 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 8, 2017):

It's only when running through ConEmu (with a custom or default config). I downloaded Vim straight from the repo's releases section (https://github.com/vim/vim-win32-installer/releases), and I got the latest version of ConEmu via the built-in automatic update feature. I'll have to verify the version of ConEmu, but I believe it's version 171025, as I updated just prior to opening the issue and that would have been the latest available version at the time. I'll try downgrading it again and verifying that the problem still exists. I'll see what I can do to repro in a fairly vanilla environment, as well.

@bgshacklett commented on GitHub (Nov 8, 2017): It's only when running through ConEmu (with a custom or default config). I downloaded Vim straight from the repo's releases section (https://github.com/vim/vim-win32-installer/releases), and I got the latest version of ConEmu via the built-in automatic update feature. I'll have to verify the version of ConEmu, but I believe it's version 171025, as I updated just prior to opening the issue and that would have been the latest available version at the time. I'll try downgrading it again and verifying that the problem still exists. I'll see what I can do to repro in a fairly vanilla environment, as well.
claunia commented 2026-01-30 21:40:06 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 10, 2017):

I've tried two versions of ConEmu: 170807 and 171025. Both of these were downloaded via the built-in update mechanism. Just for the heck of it I went and installed the "stable" version, 161206 and I was able to reproduce the problem with that version as well. No word, yet, on a repro in a a clean environment.

@bgshacklett commented on GitHub (Nov 10, 2017): I've tried two versions of ConEmu: 170807 and 171025. Both of these were downloaded via the built-in update mechanism. Just for the heck of it I went and installed the "stable" version, 161206 and I was able to reproduce the problem with that version as well. No word, yet, on a repro in a a clean environment.
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@khouzam commented on GitHub (Nov 11, 2017):

If you can attach a debugger to conhost.exe and capture a full dump of the crash we can at least get some insight on the root cause.

@khouzam commented on GitHub (Nov 11, 2017): If you can attach a debugger to conhost.exe and capture a full dump of the crash we can at least get some insight on the root cause.
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 12, 2017):

Can do. I'll report back with the details as soon as I get a moment.

@bgshacklett commented on GitHub (Nov 12, 2017): Can do. I'll report back with the details as soon as I get a moment.
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 15, 2017):

I got a memory dump today. It's available at https://1drv.ms/u/s!Arz_LjDR8MD-qxhrmA0DCkRrfchr. Please let me know if I can do anything further to help.

@bgshacklett commented on GitHub (Nov 15, 2017): I got a memory dump today. It's available at https://1drv.ms/u/s!Arz_LjDR8MD-qxhrmA0DCkRrfchr. Please let me know if I can do anything further to help.
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@khouzam commented on GitHub (Nov 15, 2017):

Thanks a lot @bgshacklett,

This is a known bug that we've had. It's been addressed and the fix will be available in a future flight.

@khouzam commented on GitHub (Nov 15, 2017): Thanks a lot @bgshacklett, This is a known bug that we've had. It's been addressed and the fix will be available in a future flight.
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 20, 2017):

@khouzam I don't suppose you might be able to provide a bit of info as to how this bug is encountered, would you? I'd like to open an issue on https://github.com/Maximus5/ConEmu, but it would be very helpful to have some information as to how to implement a workaround prior to doing so. It must be possible, as I've been using Vim with ConEmu on Windows for years; I just started having trouble recently.

Thanks!

@bgshacklett commented on GitHub (Nov 20, 2017): @khouzam I don't suppose you might be able to provide a bit of info as to how this bug is encountered, would you? I'd like to open an issue on https://github.com/Maximus5/ConEmu, but it would be very helpful to have some information as to how to implement a workaround prior to doing so. It must be possible, as I've been using Vim with ConEmu on Windows for years; I just started having trouble recently. Thanks!
claunia commented 2026-01-30 21:40:07 +00:00
Author
Owner
Copy Link

@khouzam commented on GitHub (Nov 20, 2017):

Please don't open an issue around this. This is only affecting insider builds and is a bug in the console code. It is already addressed and will make its way to insiders soon (don't know the exact flight). The usual way that the crash happens is when the buffer resizes itself, there's not much that an application could do to work around it.

@khouzam commented on GitHub (Nov 20, 2017): Please don't open an issue around this. This is only affecting insider builds and is a bug in the console code. It is already addressed and will make its way to insiders soon (don't know the exact flight). The usual way that the crash happens is when the buffer resizes itself, there's not much that an application could do to work around it.
claunia commented 2026-01-30 21:40:08 +00:00
Author
Owner
Copy Link

@bgshacklett commented on GitHub (Nov 20, 2017):

Ahh, my apologies; when you said it was a known bug I assumed that the scope was broader than just the insider builds. I'll just leave it alone and be patient, then. Thanks for the clarification!

@bgshacklett commented on GitHub (Nov 20, 2017): Ahh, my apologies; when you said it was a known bug I assumed that the scope was broader than just the insider builds. I'll just leave it alone and be patient, then. Thanks for the clarification!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Product-Conhost Work-Item
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?