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

Windows Terminal crashing when resizing panes #18717

New Issue
Closed
opened 2026-01-31 06:22:16 +00:00 by claunia · 21 comments
claunia commented 2026-01-31 06:22:16 +00:00
Owner
Copy Link

Originally created by @VanVan on GitHub (Oct 19, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.16.2642.0 ( and tested also on 1.15.2875.0)

Windows build number

Windows 11 22H2 22621.674 (Windows Feature Experience Pack 1000.22634.1000.0)

Other Software

Powershell not required, the same occur with command line

Steps to reproduce

  • Open Windows Terminal
  • Maximize window to have more space for resizing (optional but makes it easier to reproduce)
  • Split the terminal horizontally (2 pans is enough)
  • Resize right and left pane repeatedly using keyboard shortcuts Alt + Shift + Left and Alt + Shift + Right holding down the right and left keys sometimes.
  • Crash of the app and lost all pans

Expected Behavior

The panes should resize without issues

Actual Behavior

Windows Terminal crashes
We lost all pans at once

Originally created by @VanVan on GitHub (Oct 19, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.16.2642.0 ( and tested also on 1.15.2875.0) ### Windows build number Windows 11 22H2 22621.674 (Windows Feature Experience Pack 1000.22634.1000.0) ### Other Software Powershell not required, the same occur with command line ### Steps to reproduce - Open Windows Terminal - Maximize window to have more space for resizing (optional but makes it easier to reproduce) - Split the terminal horizontally (2 pans is enough) - Resize right and left pane repeatedly using keyboard shortcuts Alt + Shift + Left and Alt + Shift + Right holding down the right and left keys sometimes. - Crash of the app and lost all pans ### Expected Behavior The panes should resize without issues ### Actual Behavior Windows Terminal crashes We lost all pans at once
claunia commented 2026-01-31 06:22:18 +00:00
Author
Owner
Copy Link

@VanVan commented on GitHub (Oct 19, 2022):

This bug is not new and has been reported before but closed for lack of additional information :
https://github.com/microsoft/terminal/issues/8287

@VanVan commented on GitHub (Oct 19, 2022): This bug is not new and has been reported before but closed for lack of additional information : https://github.com/microsoft/terminal/issues/8287
claunia commented 2026-01-31 06:22:19 +00:00
Author
Owner
Copy Link

@VanVan commented on GitHub (Oct 19, 2022):

Here is a short video example of a quick crash, sometimes it's slower, and you have to move more, it's random.

https://user-images.githubusercontent.com/388581/196767243-c24c24fa-50f9-4aa9-8695-e94c4f3211cb.mp4

@VanVan commented on GitHub (Oct 19, 2022): Here is a short video example of a quick crash, sometimes it's slower, and you have to move more, it's random. https://user-images.githubusercontent.com/388581/196767243-c24c24fa-50f9-4aa9-8695-e94c4f3211cb.mp4
claunia commented 2026-01-31 06:22:19 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 19, 2022):

/feedback

@carlos-zamora commented on GitHub (Oct 19, 2022): /feedback
claunia commented 2026-01-31 06:22:19 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 19, 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 19, 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)
claunia commented 2026-01-31 06:22:19 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 19, 2022):

We're having trouble getting a repro. Could you file feedback using the steps above to help us out? That'll give us more insights as to what's going on.

@carlos-zamora commented on GitHub (Oct 19, 2022): We're having trouble getting a repro. Could you file feedback using the steps above to help us out? That'll give us more insights as to what's going on.
claunia commented 2026-01-31 06:22:20 +00:00
Author
Owner
Copy Link

@VanVan commented on GitHub (Oct 20, 2022):

Hi,
Here is the information requested.

FeedBack Hub Link

events_viewer.zip

Note that this problem does not occur on another of my computers, so there is probably some related configuration.
(Tested with default LocalState\settings.json)

@VanVan commented on GitHub (Oct 20, 2022): Hi, Here is the information requested. [FeedBack Hub Link](https://aka.ms/AAifhfi) [events_viewer.zip](https://github.com/microsoft/terminal/files/9824989/events_viewer.zip) Note that this problem does not occur on another of my computers, so there is probably some related configuration. _(Tested with default LocalState\settings.json)_
claunia commented 2026-01-31 06:22:20 +00:00
Author
Owner
Copy Link

@yurizabiyaka commented on GitHub (Nov 15, 2023):

same issue Windows Terminal Preview
Version: 1.19.2682.0
Windows 10 pro 22H2/nvidia driver 522.06

@yurizabiyaka commented on GitHub (Nov 15, 2023): same issue Windows Terminal Preview Version: 1.19.2682.0 Windows 10 pro 22H2/nvidia driver 522.06
claunia commented 2026-01-31 06:22:20 +00:00
Author
Owner
Copy Link

@nathan130200 commented on GitHub (Mar 17, 2024):

Same issue, crashing when resizing the window:

OS Version: Windows 22H2 (Build: 10.0.19045.4170)
Version: 1.19.10573.0

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error" /> 
		<EventID Qualifiers="0">1000</EventID> 
		<Version>0</Version> 
		<Level>2</Level> 
		<Task>100</Task> 
		<Opcode>0</Opcode> 
		<Keywords>0x80000000000000</Keywords> 
		<TimeCreated SystemTime="2024-03-17T15:15:02.4093899Z" /> 
		<EventRecordID>36968</EventRecordID> 
		<Correlation /> 
		<Execution ProcessID="0" ThreadID="0" /> 
		<Channel>Application</Channel> 
		<Computer>DESKTOP-75JEN6A</Computer> 
		<Security /> 
	</System>
	<EventData>
		<Data>WindowsTerminal.exe</Data> 
		<Data>1.19.2402.26003</Data> 
		<Data>65dce3ea</Data> 
		<Data>ntdll.dll</Data> 
		<Data>10.0.19041.3996</Data> 
		<Data>39215800</Data> 
		<Data>c0000409</Data> 
		<Data>00000000000a4ff8</Data> 
		<Data>1c20</Data> 
		<Data>01da787de07e564e</Data> 
		<Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> 
		<Data>C:\Windows\SYSTEM32\ntdll.dll</Data> 
		<Data>8e65b1a0-ba1e-4ba4-9e59-697701a82c32</Data> 
		<Data>Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe</Data> 
		<Data>App</Data> 
	</EventData>
</Event>
@nathan130200 commented on GitHub (Mar 17, 2024): Same issue, crashing when resizing the window: OS Version: Windows 22H2 (Build: 10.0.19045.4170) Version: 1.19.10573.0 ```cs <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-03-17T15:15:02.4093899Z" /> <EventRecordID>36968</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-75JEN6A</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.19.2402.26003</Data> <Data>65dce3ea</Data> <Data>ntdll.dll</Data> <Data>10.0.19041.3996</Data> <Data>39215800</Data> <Data>c0000409</Data> <Data>00000000000a4ff8</Data> <Data>1c20</Data> <Data>01da787de07e564e</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Windows\SYSTEM32\ntdll.dll</Data> <Data>8e65b1a0-ba1e-4ba4-9e59-697701a82c32</Data> <Data>Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia commented 2026-01-31 06:22:20 +00:00
Author
Owner
Copy Link

@mer30hamid commented on GitHub (Mar 20, 2024):

Same issue, crashing when resizing the window:

OS Version: Windows 22H2 (Build: 10.0.19045.4170) Version: 1.19.10573.0

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error" /> 
		<EventID Qualifiers="0">1000</EventID> 
		<Version>0</Version> 
		<Level>2</Level> 
		<Task>100</Task> 
		<Opcode>0</Opcode> 
		<Keywords>0x80000000000000</Keywords> 
		<TimeCreated SystemTime="2024-03-17T15:15:02.4093899Z" /> 
		<EventRecordID>36968</EventRecordID> 
		<Correlation /> 
		<Execution ProcessID="0" ThreadID="0" /> 
		<Channel>Application</Channel> 
		<Computer>DESKTOP-75JEN6A</Computer> 
		<Security /> 
	</System>
	<EventData>
		<Data>WindowsTerminal.exe</Data> 
		<Data>1.19.2402.26003</Data> 
		<Data>65dce3ea</Data> 
		<Data>ntdll.dll</Data> 
		<Data>10.0.19041.3996</Data> 
		<Data>39215800</Data> 
		<Data>c0000409</Data> 
		<Data>00000000000a4ff8</Data> 
		<Data>1c20</Data> 
		<Data>01da787de07e564e</Data> 
		<Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> 
		<Data>C:\Windows\SYSTEM32\ntdll.dll</Data> 
		<Data>8e65b1a0-ba1e-4ba4-9e59-697701a82c32</Data> 
		<Data>Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe</Data> 
		<Data>App</Data> 
	</EventData>
</Event>

I have disabled Use the new text renderer ("AtlasEngine") and this fixed this problem !
image

@mer30hamid commented on GitHub (Mar 20, 2024): > Same issue, crashing when resizing the window: > > OS Version: Windows 22H2 (Build: 10.0.19045.4170) Version: 1.19.10573.0 > > ```cs > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> > <System> > <Provider Name="Application Error" /> > <EventID Qualifiers="0">1000</EventID> > <Version>0</Version> > <Level>2</Level> > <Task>100</Task> > <Opcode>0</Opcode> > <Keywords>0x80000000000000</Keywords> > <TimeCreated SystemTime="2024-03-17T15:15:02.4093899Z" /> > <EventRecordID>36968</EventRecordID> > <Correlation /> > <Execution ProcessID="0" ThreadID="0" /> > <Channel>Application</Channel> > <Computer>DESKTOP-75JEN6A</Computer> > <Security /> > </System> > <EventData> > <Data>WindowsTerminal.exe</Data> > <Data>1.19.2402.26003</Data> > <Data>65dce3ea</Data> > <Data>ntdll.dll</Data> > <Data>10.0.19041.3996</Data> > <Data>39215800</Data> > <Data>c0000409</Data> > <Data>00000000000a4ff8</Data> > <Data>1c20</Data> > <Data>01da787de07e564e</Data> > <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> > <Data>C:\Windows\SYSTEM32\ntdll.dll</Data> > <Data>8e65b1a0-ba1e-4ba4-9e59-697701a82c32</Data> > <Data>Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe</Data> > <Data>App</Data> > </EventData> > </Event> > ``` I have disabled `Use the new text renderer ("AtlasEngine")` and this fixed this problem ! ![image](https://github.com/microsoft/terminal/assets/1561497/7f194fb0-d33c-4c1b-afde-fd258e27ab8a)
claunia commented 2026-01-31 06:22:20 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 20, 2024):

@mer30hamid The option to disable AtlasEngine will go away in the future. Could you please assist me in figuring out why it crashes? To do so, please enable AtlasEngine again and send me a crash dump. You can find my email address in my GitHub profile. Here's how to enable crash dumps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

@lhecker commented on GitHub (Mar 20, 2024): @mer30hamid The option to disable AtlasEngine will go away in the future. Could you please assist me in figuring out why it crashes? To do so, please enable AtlasEngine again and send me a crash dump. You can find my email address in my GitHub profile. Here's how to enable crash dumps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically
claunia commented 2026-01-31 06:22:21 +00:00
Author
Owner
Copy Link

@mer30hamid commented on GitHub (Mar 20, 2024):

@mer30hamid The option to disable AtlasEngine will go away in the future. Could you please assist me in figuring out why it crashes? To do so, please enable AtlasEngine again and send me a crash dump. You can find my email address in my GitHub profile. Here's how to enable crash dumps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

Done.

@mer30hamid commented on GitHub (Mar 20, 2024): > @mer30hamid The option to disable AtlasEngine will go away in the future. Could you please assist me in figuring out why it crashes? To do so, please enable AtlasEngine again and send me a crash dump. You can find my email address in my GitHub profile. Here's how to enable crash dumps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically Done.
claunia commented 2026-01-31 06:22:21 +00:00
Author
Owner
Copy Link

@nathan130200 commented on GitHub (Mar 21, 2024):

@mer30hamid I've tried didn't worked. I can fix this when i enable software rendering instead of hardware rendering.

After resize, the callstack of crash (i attached vs2022 debugger into crashdump):


 ucrtbase.dll!00007ffc23dcfde6()Unknown
Microsoft.Terminal.Control.dll!operator new(unsigned __int64 size) Line 36C++
 [Inline Frame] Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::Buffer<DWRITE_GLYPH_OFFSET,4>::allocate(unsigned __int64) Line 276C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::Buffer<DWRITE_GLYPH_OFFSET,4>::Buffer<DWRITE_GLYPH_OFFSET,4>(unsigned __int64 size) Line 166C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::_recreateCellCountDependentResources() Line 595C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::_handleSettingsUpdate() Line 527C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::StartPaint() Line 81C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Renderer::_PaintFrameForEngine(Microsoft::Console::Render::IRenderEngine * const pEngine) Line 122C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Renderer::PaintFrame() Line 78C++
 Microsoft.Terminal.Control.dll!Microsoft::Console::Render::RenderThread::_ThreadProc() Line 217C++

I managed to combine the options between software rendering/atlas engine to get this results:

Atlas Engine Software Rendering Crash?
On On No
On Off Yes
Off Yes No
Off Off No

Also if i hit multiple times Save button while atlas engine is enabled, also make terminal crash.

VS debugger also points to here as the crash reason:

image

@nathan130200 commented on GitHub (Mar 21, 2024): @mer30hamid I've tried didn't worked. I can fix this when i enable **software rendering** instead of hardware rendering. After resize, the callstack of crash (i attached vs2022 debugger into crashdump): ```cs ucrtbase.dll!00007ffc23dcfde6()Unknown Microsoft.Terminal.Control.dll!operator new(unsigned __int64 size) Line 36C++ [Inline Frame] Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::Buffer<DWRITE_GLYPH_OFFSET,4>::allocate(unsigned __int64) Line 276C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::Buffer<DWRITE_GLYPH_OFFSET,4>::Buffer<DWRITE_GLYPH_OFFSET,4>(unsigned __int64 size) Line 166C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::_recreateCellCountDependentResources() Line 595C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::_handleSettingsUpdate() Line 527C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Atlas::AtlasEngine::StartPaint() Line 81C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Renderer::_PaintFrameForEngine(Microsoft::Console::Render::IRenderEngine * const pEngine) Line 122C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::Renderer::PaintFrame() Line 78C++ Microsoft.Terminal.Control.dll!Microsoft::Console::Render::RenderThread::_ThreadProc() Line 217C++ ``` I managed to combine the options between software rendering/atlas engine to get this results: | Atlas Engine | Software Rendering | Crash? | |--------------|--------------------|--------| | On | On | No | | On | Off | Yes | | Off | Yes | No | | Off | Off | No | Also if i hit multiple times `Save` button while atlas engine is enabled, also make terminal crash. VS debugger also points to here as the crash reason: ![image](https://github.com/microsoft/terminal/assets/14365254/f8b84bc5-5a4f-4c86-9f6f-743f5c05f721)
claunia commented 2026-01-31 06:22:21 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 21, 2024):

@mer30hamid Thanks! Your terminal is crashing due to a heap corruption. Unfortunately I can't tell what's corrupting your heap. Would you be willing to help me further test this?

If so, one thing I'd like to test is whether Windows Terminal Canary crashes for you. You can install it here: https://aka.ms/terminal-canary-installer
After installing it, make sure it has imported all your settings from your regular Windows Terminal. (Otherwise open the settings file with Ctrl+Shift+, in both applications and copy it over.)

@lhecker commented on GitHub (Mar 21, 2024): @mer30hamid Thanks! Your terminal is crashing due to a heap corruption. Unfortunately I can't tell what's corrupting your heap. Would you be willing to help me further test this? If so, one thing I'd like to test is whether Windows Terminal Canary crashes for you. You can install it here: https://aka.ms/terminal-canary-installer After installing it, make sure it has imported all your settings from your regular Windows Terminal. (Otherwise open the settings file with Ctrl+Shift+, in both applications and copy it over.)
claunia commented 2026-01-31 06:22:21 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 21, 2024):

@nathan130200 Your crash is super interesting! Would it be possible to share that crashdump with me? You can find my email address in my GitHub profile. Otherwise, could you tell me what the value of the size parameter is?

@lhecker commented on GitHub (Mar 21, 2024): @nathan130200 Your crash is super interesting! Would it be possible to share that crashdump with me? You can find my email address in my GitHub profile. Otherwise, could you tell me what the value of the `size` parameter is?
claunia commented 2026-01-31 06:22:22 +00:00
Author
Owner
Copy Link

@mer30hamid commented on GitHub (Mar 21, 2024):

@mer30hamid Thanks! Your terminal is crashing due to a heap corruption. Unfortunately I can't tell what's corrupting your heap. Would you be willing to help me further test this?

If so, one thing I'd like to test is whether Windows Terminal Canary crashes for you. You can install it here: https://aka.ms/terminal-canary-installer After installing it, make sure it has imported all your settings from your regular Windows Terminal. (Otherwise open the settings file with Ctrl+Shift+, in both applications and copy it over.)

I can't install it because my windows version is: windows 10 22H2 Build 19045.4170 and I get this error:

App installation failed with error message: Windows cannot install package Microsoft.WindowsTerminalCanary_1.21.803.0_x64__8wekyb3d8bbwe because this package is not compatible with the device. The package requires OS version 10.0.22000.0 or higher on the Windows.Desktop device family. The device is currently running OS version 10.0.19045.4170. (0x80073cfd)

p.s: When I enable use software rendering the crash does not accur

@mer30hamid commented on GitHub (Mar 21, 2024): > @mer30hamid Thanks! Your terminal is crashing due to a heap corruption. Unfortunately I can't tell what's corrupting your heap. Would you be willing to help me further test this? > > If so, one thing I'd like to test is whether Windows Terminal Canary crashes for you. You can install it here: https://aka.ms/terminal-canary-installer After installing it, make sure it has imported all your settings from your regular Windows Terminal. (Otherwise open the settings file with Ctrl+Shift+, in both applications and copy it over.) I can't install it because my windows version is: `windows 10 22H2 Build 19045.4170` and I get this error: ``` App installation failed with error message: Windows cannot install package Microsoft.WindowsTerminalCanary_1.21.803.0_x64__8wekyb3d8bbwe because this package is not compatible with the device. The package requires OS version 10.0.22000.0 or higher on the Windows.Desktop device family. The device is currently running OS version 10.0.19045.4170. (0x80073cfd) ``` p.s: When I enable `use software rendering ` the crash does not accur
claunia commented 2026-01-31 06:22:22 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 21, 2024):

@mer30hamid Ah sorry, I forgot that the appinstaller had this limitation. I believe the portable .zip should work though. You can get it here: https://aka.ms/terminal-canary-zip-x64

@lhecker commented on GitHub (Mar 21, 2024): @mer30hamid Ah sorry, I forgot that the appinstaller had this limitation. I believe the portable .zip should work though. You can get it here: https://aka.ms/terminal-canary-zip-x64
claunia commented 2026-01-31 06:22:22 +00:00
Author
Owner
Copy Link

@mer30hamid commented on GitHub (Mar 22, 2024):

@mer30hamid Ah sorry, I forgot that the appinstaller had this limitation. I believe the portable .zip should work though. You can get it here: https://aka.ms/terminal-canary-zip-x64

I sent you the crash dump for this version, turning the "Use software rendering" option to "on" , solved the problem again!

@mer30hamid commented on GitHub (Mar 22, 2024): > @mer30hamid Ah sorry, I forgot that the appinstaller had this limitation. I believe the portable .zip should work though. You can get it here: https://aka.ms/terminal-canary-zip-x64 I sent you the crash dump for this version, turning the "Use software rendering" option to "on" , solved the problem again!
claunia commented 2026-01-31 06:22:22 +00:00
Author
Owner
Copy Link

@nathan130200 commented on GitHub (Mar 25, 2024):

@lhecker the size param value is 331, combined with sizeof(DWRITE_GLYPH_OFFSET) * size value is 2648.

Update: I've checked here and if i let windows choose prefered GPU for Terminal, then will use my onboard-gpu and will trigger the crash if Enable software rendering is not enabled while resizing the window. While i manually set to windows use my offboard gpu, don't crash Terminal.

I will send the crashdump.

@nathan130200 commented on GitHub (Mar 25, 2024): @lhecker the `size` param value is 331, combined with `sizeof(DWRITE_GLYPH_OFFSET) * size` value is 2648. Update: I've checked here and if i let windows choose prefered GPU for Terminal, then will use my onboard-gpu and will trigger the crash if `Enable software rendering` is not enabled while resizing the window. While i manually set to windows use my offboard gpu, don't crash Terminal. I will send the crashdump.
claunia commented 2026-01-31 06:22:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 25, 2024):

@nathan130200 Thanks for the dump! It's very helpful, since it contains a reference to the entire AtlasEngine instance at the time of the crash. I've written a response here: https://github.com/microsoft/terminal/issues/16747#issuecomment-2017980996
In your case, I would recommend to continue using your Nvidia GPU.

By the way, since you say "onboard-gpu", are you sure your have your monitor plugged into your Nvidia GPU? Because if you did, Windows Terminal should've been using your Nvidia GPU by default. I would suggest checking that. 🙂

@lhecker commented on GitHub (Mar 25, 2024): @nathan130200 Thanks for the dump! It's very helpful, since it contains a reference to the entire AtlasEngine instance at the time of the crash. I've written a response here: https://github.com/microsoft/terminal/issues/16747#issuecomment-2017980996 In your case, I would recommend to continue using your Nvidia GPU. By the way, since you say "onboard-gpu", are you sure your have your monitor plugged into your Nvidia GPU? Because if you did, Windows Terminal should've been using your Nvidia GPU by default. I would suggest checking that. 🙂
claunia commented 2026-01-31 06:22:23 +00:00
Author
Owner
Copy Link

@nathan130200 commented on GitHub (Mar 25, 2024):

I've said "on-board GPU" because its a laptop GPU (the chip is soldered onto the motherboard itself), then windows keep switing between HD Graphics (default for non 3d/2d/graphics related) and GeForce 710M (when using directx/opengl stuff).

https://github.com/microsoft/terminal/assets/14365254/562c76b5-7851-42dd-b688-cbe439e1dfb9

@nathan130200 commented on GitHub (Mar 25, 2024): I've said "on-board GPU" because its a laptop GPU (the chip is soldered onto the motherboard itself), then windows keep switing between HD Graphics (default for non 3d/2d/graphics related) and GeForce 710M (when using directx/opengl stuff). https://github.com/microsoft/terminal/assets/14365254/562c76b5-7851-42dd-b688-cbe439e1dfb9
claunia commented 2026-01-31 06:22:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 25, 2024):

I have another idea why this may occur and will add a bunch of settings to the Rendering tab to give users more control over this. 🙂

@lhecker commented on GitHub (Mar 25, 2024): I have another idea why this may occur and will add a bunch of settings to the Rendering tab to give users more control over this. 🙂
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 Area-TerminalControl Issue-Bug Needs-Attention Needs-Repro Needs-Tag-Fix Product-Terminal Severity-Crash
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#18717
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?