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

Built Windows Terminal asserts with an abort() #641

New Issue
Closed
opened 2026-01-30 21:57:47 +00:00 by claunia · 19 comments
claunia commented 2026-01-30 21:57:47 +00:00
Owner
Copy Link

Originally created by @rkeithhill on GitHub (May 6, 2019).

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Windows 10 1809 (17763.475)

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    Built the repo using the instructions in the readme (w/VS 2017 x86 native prompt). When I run Debug\WindowsTerminal.exe I get this error:

image

  • What's wrong / what should be happening instead:
    The app should start unless I need to be on a newer version of Windows?
Originally created by @rkeithhill on GitHub (May 6, 2019). This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: (Type `ver` at a Windows Command Prompt) Windows 10 1809 (17763.475) * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Built the repo using the instructions in the readme (w/VS 2017 x86 native prompt). When I run `Debug\WindowsTerminal.exe` I get this error: ![image](https://user-images.githubusercontent.com/5177512/57248616-05bb9080-7000-11e9-9d7e-7268d01a5286.png) * What's wrong / what should be happening instead: The app should start unless I need to be on a newer version of Windows?
claunia commented 2026-01-30 21:57:48 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 6, 2019):

Psychic debugging says you're trying to use x86 on an amd64 machine. Build the other architecture.

Actual debugging, can you do the Retry button and get me the stack?

@miniksa commented on GitHub (May 6, 2019): Psychic debugging says you're trying to use x86 on an amd64 machine. Build the other architecture. Actual debugging, can you do the Retry button and get me the stack?
claunia commented 2026-01-30 21:57:48 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

What version of VS do you recommend to build with? I have both VS 2017 and VS 2019. Also, 32-bit binaries normally run just fine on 64-bit Windows.

@rkeithhill commented on GitHub (May 6, 2019): What version of VS do you recommend to build with? I have both VS 2017 and VS 2019. Also, 32-bit binaries normally run just fine on 64-bit Windows.
claunia commented 2026-01-30 21:57:48 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 6, 2019):

VS 2017 is what I use, but I should probably move over to 2019. I've heard from others on the team that it works in both.

This is a little different because the console host is a part of the package to provide bleeding-edge conpty support to the Windows Terminal application. The console host has to match architecture of the underlying system.

@miniksa commented on GitHub (May 6, 2019): VS 2017 is what I use, but I should probably move over to 2019. I've heard from others on the team that it works in both. This is a little different because the console host is a part of the package to provide bleeding-edge conpty support to the Windows Terminal application. The console host has to match architecture of the underlying system.
claunia commented 2026-01-30 21:57:48 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

image

image

This is with WindowsTerminal (Windows Store 10.0) set as the startup project.

@rkeithhill commented on GitHub (May 6, 2019): ![image](https://user-images.githubusercontent.com/5177512/57250584-0efb2c00-7005-11e9-96e5-3177d9fdf9e9.png) ![image](https://user-images.githubusercontent.com/5177512/57250594-17536700-7005-11e9-9743-b07a4bb19e23.png) This is with `WindowsTerminal (Windows Store 10.0)` set as the startup project.
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

Oh, you're gonna want to set CascadiaPackage as the startup project

@zadjii-msft commented on GitHub (May 6, 2019): Oh, you're gonna want to set CascadiaPackage as the startup project
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

Ah, and I do need to be on a newer version of Windows 10:

image

Is that 1903 or post 1903? I'm pretty sure that is 1903. I'm going to try this on my Windows 10 Insiders machine (running 18890).

@rkeithhill commented on GitHub (May 6, 2019): Ah, and I do need to be on a newer version of Windows 10: ![image](https://user-images.githubusercontent.com/5177512/57250805-85982980-7005-11e9-8778-a55c59df179c.png) Is that `1903` or post `1903`? I'm pretty sure that is `1903`. I'm going to try this on my Windows 10 Insiders machine (running 18890).
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

Might want to update the readme with a few basic prereqs like:

  • Windows 10 1903 or later
  • Enable Windows Developer Mode
  • Visual Studio 2017 (with desktop C++ and UWP workloads installed)
@rkeithhill commented on GitHub (May 6, 2019): Might want to update the readme with a few basic prereqs like: * Windows 10 1903 or later * Enable Windows Developer Mode * Visual Studio 2017 (with desktop C++ and UWP workloads installed)
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@codecat commented on GitHub (May 6, 2019):

I saw you editing your comment.. :) So it does require 1903? OpenConsole.exe just opens a regular old cmd on my machine. (Still running 1803 though..)

@codecat commented on GitHub (May 6, 2019): I saw you editing your comment.. :) So it does require 1903? `OpenConsole.exe` just opens a regular old cmd on my machine. (Still running 1803 though..)
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

Yeah, OpenConsole.exe does not seem to be the interesting exe.

@rkeithhill commented on GitHub (May 6, 2019): Yeah, `OpenConsole.exe` does not seem to be **the** interesting exe.
claunia commented 2026-01-30 21:57:49 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 6, 2019):

OpenConsole.exe will work on things before 1903, but is "not the interesting EXE" in that it is not where the Terminal is. It is where the console host is, however, including the PTY engine and all the other services required to make this work. So in that way, it is interesting to some degree.

You should probably be on 1903 to get the whole Windows Terminal going.

And yes, we should probably update the README. We're a bit inundated today and this week with Build, so I'd be happy to take a PR with those changes if you want to send it!

@miniksa commented on GitHub (May 6, 2019): `OpenConsole.exe` will work on things before 1903, but is "not the interesting EXE" in that it is not where the Terminal is. It is where the console host is, however, including the PTY engine and all the other services required to make this work. So in that way, it is interesting to some degree. You should probably be on 1903 to get the whole Windows Terminal going. And yes, we should probably update the README. We're a bit inundated today and this week with Build, so I'd be happy to take a PR with those changes if you want to send it!
claunia commented 2026-01-30 21:57:50 +00:00
Author
Owner
Copy Link

@bschoepke commented on GitHub (May 6, 2019):

I'm on a 1903 build (internal, 18865) and still see the old cmd.exe when I run Cascadia

@bschoepke commented on GitHub (May 6, 2019): I'm on a 1903 build (internal, 18865) and still see the old cmd.exe when I run Cascadia
claunia commented 2026-01-30 21:57:50 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

It looks like the terminal is a UWP/Store app so then it is true that you need to enable Windows Developer Mode in order to side-load the app?

@rkeithhill commented on GitHub (May 6, 2019): It looks like the terminal is a UWP/Store app so then it is true that you need to enable Windows Developer Mode in order to side-load the app?
claunia commented 2026-01-30 21:57:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

@bschoepke try pressing ctrl+t

The default settings for winterm right now are specifically designed to make it look like conhost+cmd.exe out of the box.

@zadjii-msft commented on GitHub (May 6, 2019): @bschoepke try pressing ctrl+t The default settings for winterm right now are specifically designed to make it look like conhost+cmd.exe out of the box.
claunia commented 2026-01-30 21:57:50 +00:00
Author
Owner
Copy Link

@bschoepke commented on GitHub (May 6, 2019):

Pressing Ctrl + T does indeed show the XAML tab bar and settings menu, thanks.

@bschoepke commented on GitHub (May 6, 2019): Pressing Ctrl + T does indeed show the XAML tab bar and settings menu, thanks.
claunia commented 2026-01-30 21:57:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

@rkeithhill I believe that's correct, but I haven't had Developer Mode disabled in the longest time, so I can't be sure.

@bschoepke I'll make a note of that in the README

@zadjii-msft commented on GitHub (May 6, 2019): @rkeithhill I believe that's correct, but I haven't had Developer Mode disabled in the longest time, so I can't be sure. @bschoepke I'll make a note of that in the README
claunia commented 2026-01-30 21:57:51 +00:00
Author
Owner
Copy Link

@keithn commented on GitHub (May 6, 2019):

I seem to be having a LOT of problems trying to build it in 2019, I completely uinstalled 2017, but it seems there is various dependencies on 2017 packages, I tried retargetting, but seems to be a bunch of dependences that don't get sorted out....

UPDATE: sorry, no, seemed to default to AMD for the build

UPDATE: Still won't compile though, giving up now until the repo is updated to 2019 :)

@keithn commented on GitHub (May 6, 2019): I seem to be having a LOT of problems trying to build it in 2019, I completely uinstalled 2017, but it seems there is various dependencies on 2017 packages, I tried retargetting, but seems to be a bunch of dependences that don't get sorted out.... UPDATE: sorry, no, seemed to default to AMD for the build UPDATE: Still won't compile though, giving up now until the repo is updated to 2019 :)
claunia commented 2026-01-30 21:57:51 +00:00
Author
Owner
Copy Link

@matthew4850 commented on GitHub (May 6, 2019):

I was able to get it to compile, see my reply in #435

@matthew4850 commented on GitHub (May 6, 2019): I was able to get it to compile, see my reply in #435
claunia commented 2026-01-30 21:57:51 +00:00
Author
Owner
Copy Link

@shuffle2 commented on GitHub (May 7, 2019):

@zadjii-msft is there a reason it isn't just made the default in the .sln file? (first listed project should become default startup project, normally..)

I decreased the version in CascadiaPackage/Package.appxmanifest to 10.0.17763.404, and the app crashes on launch now:

 	TerminalApp.dll!winrt::impl::consume_Microsoft_UI_Xaml_Controls_ITabViewFactory<winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory>::CreateInstance(const winrt::Windows::Foundation::IInspectable & baseInterface, winrt::Windows::Foundation::IInspectable & innerInterface) Line 5196	C++
 	TerminalApp.dll!<lambda_8456af98b166b0be9dea16317fc91623>::operator()<winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory const &>(const winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory & f) Line 18959	C++
 	TerminalApp.dll!winrt::impl::factory_cache_entry<winrt::Microsoft::UI::Xaml::Controls::TabView,winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory>::call<<lambda_8456af98b166b0be9dea16317fc91623> &>(winrt::Microsoft::UI::Xaml::Controls::TabView::{ctor}::__l2::<lambda_8456af98b166b0be9dea16317fc91623> & callback) Line 5440	C++
 	TerminalApp.dll!winrt::impl::call_factory<winrt::Microsoft::UI::Xaml::Controls::TabView,winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory,<lambda_8456af98b166b0be9dea16317fc91623> >(winrt::Microsoft::UI::Xaml::Controls::TabView::{ctor}::__l2::<lambda_8456af98b166b0be9dea16317fc91623> && callback) Line 5501	C++
 	TerminalApp.dll!winrt::Microsoft::UI::Xaml::Controls::TabView::TabView() Line 18959	C++
 	TerminalApp.dll!winrt::TerminalApp::implementation::App::_Create() Line 85	C++
 	TerminalApp.dll!winrt::TerminalApp::implementation::App::Create() Line 70	C++
 	TerminalApp.dll!winrt::impl::produce<winrt::TerminalApp::implementation::App,winrt::TerminalApp::IApp>::Create() Line 428	C++
 	WindowsTerminal.exe!winrt::impl::consume_TerminalApp_IApp<winrt::TerminalApp::IApp>::Create() Line 18	C++
 	WindowsTerminal.exe!AppHost::Initialize() Line 72	C++
 	WindowsTerminal.exe!wWinMain(HINSTANCE__ * __formal, HINSTANCE__ * __formal, wchar_t * __formal, int __formal) Line 46	C++

Exception thrown: read access violation.
pPLMHandler was nullptr.

It also took quite a while to figure out what packages had to be installed via the VS2017 Installer. I wound up installing ~11GB of crap I probably don't need. It would be great to have a min list / script to do that.

fun...

edit: I saw #429 now. I had to manually install some things besides just

  • "Desktop Development with C++"
  • "Universal Windows Platform Development"

, unfortunately.

Also, is running OS build >= 10.0.18362.0 a real hard requirement? (...that would be kinda dumbfounding). I'd just wait for a public release of 1903, then :/

@shuffle2 commented on GitHub (May 7, 2019): @zadjii-msft is there a reason it isn't just made the default in the .sln file? (first listed project should become default startup project, normally..) I decreased the version in CascadiaPackage/Package.appxmanifest to 10.0.17763.404, and the app crashes on launch now: ``` TerminalApp.dll!winrt::impl::consume_Microsoft_UI_Xaml_Controls_ITabViewFactory<winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory>::CreateInstance(const winrt::Windows::Foundation::IInspectable & baseInterface, winrt::Windows::Foundation::IInspectable & innerInterface) Line 5196 C++ TerminalApp.dll!<lambda_8456af98b166b0be9dea16317fc91623>::operator()<winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory const &>(const winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory & f) Line 18959 C++ TerminalApp.dll!winrt::impl::factory_cache_entry<winrt::Microsoft::UI::Xaml::Controls::TabView,winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory>::call<<lambda_8456af98b166b0be9dea16317fc91623> &>(winrt::Microsoft::UI::Xaml::Controls::TabView::{ctor}::__l2::<lambda_8456af98b166b0be9dea16317fc91623> & callback) Line 5440 C++ TerminalApp.dll!winrt::impl::call_factory<winrt::Microsoft::UI::Xaml::Controls::TabView,winrt::Microsoft::UI::Xaml::Controls::ITabViewFactory,<lambda_8456af98b166b0be9dea16317fc91623> >(winrt::Microsoft::UI::Xaml::Controls::TabView::{ctor}::__l2::<lambda_8456af98b166b0be9dea16317fc91623> && callback) Line 5501 C++ TerminalApp.dll!winrt::Microsoft::UI::Xaml::Controls::TabView::TabView() Line 18959 C++ TerminalApp.dll!winrt::TerminalApp::implementation::App::_Create() Line 85 C++ TerminalApp.dll!winrt::TerminalApp::implementation::App::Create() Line 70 C++ TerminalApp.dll!winrt::impl::produce<winrt::TerminalApp::implementation::App,winrt::TerminalApp::IApp>::Create() Line 428 C++ WindowsTerminal.exe!winrt::impl::consume_TerminalApp_IApp<winrt::TerminalApp::IApp>::Create() Line 18 C++ WindowsTerminal.exe!AppHost::Initialize() Line 72 C++ WindowsTerminal.exe!wWinMain(HINSTANCE__ * __formal, HINSTANCE__ * __formal, wchar_t * __formal, int __formal) Line 46 C++ ``` ``` Exception thrown: read access violation. pPLMHandler was nullptr. ``` It also took quite a while to figure out what packages had to be installed via the VS2017 Installer. I wound up installing ~11GB of crap I probably don't need. It would be great to have a min list / script to do that. fun... edit: I saw #429 now. I had to manually install some things besides just > - "Desktop Development with C++" > - "Universal Windows Platform Development" , unfortunately. Also, is running OS build >= 10.0.18362.0 a real hard requirement? (...that would be kinda dumbfounding). I'd just wait for a public release of 1903, then :/
claunia commented 2026-01-30 21:57:51 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 14, 2019):

OK. This has turned into a grab bag of assorted build issues and many of them are already resolved. The rest of it is trying to move versions down which we don't support. I'll close this in favor of the other issues hanging around.

@miniksa commented on GitHub (May 14, 2019): OK. This has turned into a grab bag of assorted build issues and many of them are already resolved. The rest of it is trying to move versions down which we don't support. I'll close this in favor of the other issues hanging around.
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
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#641
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?