-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Windows Terminal crashing when resizing panes #14254
Comments
This bug is not new and has been reported before but closed for lack of additional information : |
Here is a short video example of a quick crash, sometimes it's slower, and you have to move more, it's random. Invite.de.commandes.2022-10-19.19-43-07.mp4 |
/feedback |
Hi there! |
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. |
Hi, Note that this problem does not occur on another of my computers, so there is probably some related configuration. |
same issue Windows Terminal Preview |
Same issue, crashing when resizing the window: OS Version: Windows 22H2 (Build: 10.0.19045.4170) <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> |
@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 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:
Also if i hit multiple times VS debugger also points to here as the crash reason: |
@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 |
@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 |
I can't install it because my windows version is:
p.s: When I enable |
@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! |
@lhecker the 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 I will send the crashdump. |
@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: #16747 (comment) 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. 🙂 |
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). ApplicationFrameHost_DtREjhOyst.mp4 |
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. 🙂 |
This implements `SetForceFullRepaintRendering` and adds a new `SetGraphicsAPI` function. The former toggles `Present1` on and off and the latter allows users to explicitly request Direct2D/3D. On top of these changes I did a minor cleanup of the interface, because now that DxRenderer is gone we don't need all that anymore. Closes #14254 Closes #16747 ## Validation Steps Performed * Toggling Direct2D on/off changes colored ligature support ✅ * Toggling Present1 on/off can be observed in a debugger ✅ * Toggling WARP on/off changes GPU metrics ✅ --------- Co-authored-by: Dustin L. Howett <duhowett@microsoft.com>
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
Expected Behavior
The panes should resize without issues
Actual Behavior
Windows Terminal crashes
We lost all pans at once
The text was updated successfully, but these errors were encountered: