Terminal Crashes with side-by-side windows in same tab after resize #18624

Closed
opened 2026-01-31 06:19:34 +00:00 by claunia · 4 comments
Owner

Originally created by @milt0r on GitHub (Oct 8, 2022).

Windows Terminal version

1.15.2713.0

Windows build number

10.0.22623.0

Other Software

Using Windows SSH client

Steps to reproduce

  1. Open Terminal to default PowerShell tab
  2. Click profiles dropdown and select a tab that runs: SSH user@hostname
  3. Click dropdown again and alt-click on the same profile. It opens side-by-side.
  4. Resize the window.

Crashes.

Expected Behavior

No crash :)

Actual Behavior

It crashes upon dragging the corner and resizing.

Originally created by @milt0r on GitHub (Oct 8, 2022). ### Windows Terminal version 1.15.2713.0 ### Windows build number 10.0.22623.0 ### Other Software Using Windows SSH client ### Steps to reproduce 1. Open Terminal to default PowerShell tab 2. Click profiles dropdown and select a tab that runs: SSH user@hostname 3. Click dropdown again and alt-click on the same profile. It opens side-by-side. 4. Resize the window. Crashes. ### Expected Behavior No crash :) ### Actual Behavior It crashes upon dragging the corner and resizing.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:19:35 +00:00
Author
Owner

@lhecker commented on GitHub (Oct 10, 2022):

I wasn't able to reproduce the issue with the instructions you've provided. A Feedback Hub trace of the crash might be helpful: /feedback

@lhecker commented on GitHub (Oct 10, 2022): I wasn't able to reproduce the issue with the instructions you've provided. A Feedback Hub trace of the crash might be helpful: /feedback
Author
Owner

@ghost commented on GitHub (Oct 10, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Oct 10, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@milt0r commented on GitHub (Oct 10, 2022):

This looks like an issue on my machine. I looked at the crash message and see this:

Faulting application name: WindowsTerminal.exe, version: 1.15.2209.28003, time stamp: 0x6334cd9b
Faulting module name: NahimicOSD.dll, version: 2.2.23.0, time stamp: 0x61b7fd89
Exception code: 0xc0000005
Fault offset: 0x00000000000169a2
Faulting process id: 0x0x9304
Faulting application start time: 0x0x1D8DCD793C7D50A
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\NahimicOSD.dll
Report Id: c1433188-ca40-43db-bde9-6f9abc722e69
Faulting package full name: Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Will also submit feedback.

@milt0r commented on GitHub (Oct 10, 2022): This looks like an issue on my machine. I looked at the crash message and see this: Faulting application name: WindowsTerminal.exe, version: 1.15.2209.28003, time stamp: 0x6334cd9b Faulting module name: NahimicOSD.dll, version: 2.2.23.0, time stamp: 0x61b7fd89 Exception code: 0xc0000005 Fault offset: 0x00000000000169a2 Faulting process id: 0x0x9304 Faulting application start time: 0x0x1D8DCD793C7D50A Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe **Faulting module path: C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\NahimicOSD.dll** Report Id: c1433188-ca40-43db-bde9-6f9abc722e69 Faulting package full name: Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Will also submit feedback.
Author
Owner

@DHowett commented on GitHub (Oct 10, 2022):

Hey, we've actually seen crashes with A-Volute before! They are injecting a DLL into every application, and it seems like it is not stable.

I've gotta close this one out since it's not on our end; the best way to get support is unfortunately to go bother A-Volute. We've also done the same 😄 so we're approaching it from both angles.

@DHowett commented on GitHub (Oct 10, 2022): Hey, we've actually seen crashes with A-Volute before! They are injecting a DLL into every application, and it seems like it is _not stable_. I've gotta close this one out since it's not on our end; the best way to get support is unfortunately to go bother A-Volute. We've also done the same :smile: so we're approaching it from both angles.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18624