starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-23 23:45:08 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Access Violation #4628

New Issue
Closed
opened 2026-01-30 23:52:20 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 23:52:20 +00:00
Owner
Copy Link

Originally created by @jeffrson on GitHub (Oct 24, 2019).

Environment

Windows build number: 10.0.18362.356
Windows Terminal version: 0.5.2762

Steps to reproduce

After some action (not reproducible - call stack not analyzed previously, so I don't know if it's always the same) the postmortem WinDbg is triggered.

Expected behavior

No crash.

Actual behavior

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_TerminalControl.dll!Unknown

BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ

STACK_TEXT:  
00000091`1fd7f4e0 00007ffa`fff78aec : 00000285`7d213230 00000000`00000012 00000000`00000000 00007ffb`6c0ffc2c : TerminalControl+0x7ea1
00000091`1fd7f550 00007ffb`65c35ef1 : 00000000`00000000 00000285`878d6bf0 00000285`8a4ed300 00000000`00000000 : TerminalControl+0x18aec
00000091`1fd7f5a0 00007ffb`65eefba6 : 00000285`8a401d40 00000285`878d6bf0 00000285`7d0b0340 00000285`00c00040 : Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_59517943c03487243f9bea31c6c1a784>,-1>::Invoke+0x71
00000091`1fd7f5d0 00007ffb`65ebbd46 : 00000285`7d30ba80 00000285`8a4ed300 00000285`7d30ba80 00000285`8a4ed300 : CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback+0x16
00000091`1fd7f600 00007ffb`65ebae8d : 00000285`7d252ca0 00000285`7d30bcd0 00000285`8a4ed300 00000285`886f2580 : CoreMessaging!Microsoft__CoreUI__Dispatch__TimeoutHandler$CallbackThunk+0x186
00000091`1fd7f680 00007ffb`65eba818 : 00000285`886f2580 00000285`875eaa40 00000285`886f2580 00000285`7d30bb60 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch+0x2bd
00000091`1fd7f730 00007ffb`65ec1108 : 00000000`00000003 00000285`7d235d00 00000285`7d235d00 00000000`00000003 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch+0x158
00000091`1fd7f7a0 00007ffb`65ec0491 : 00000285`7d252ca0 00000091`1fd7f8d8 00000285`7d310b60 00000285`7d251bf0 : CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0xa68
00000091`1fd7f880 00007ffb`65ebfd99 : 00000285`7d251bf0 00000285`7d313220 00000000`00000000 00000000`00000000 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1d1
00000091`1fd7f970 00007ffb`65ebfbcb : 00000000`00000000 00000285`7d313220 00000000`00000000 00000000`40000c02 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_DoWork+0xe9
00000091`1fd7fa50 00007ffb`6b13681d : 00000000`00000002 00000000`80000022 00000000`00000001 00000091`1fd7fe69 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_WindowProc+0x9b
00000091`1fd7fa80 00007ffb`6b1363ec : 00000000`00008388 00007ffb`65ebfb30 00000000`000f0a18 00000000`80000000 : USER32!UserCallWinProcCheckWow+0x2bd
00000091`1fd7fc10 00007ffb`6b142d03 : 00000091`1fd7fe40 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0x9c
00000091`1fd7fc70 00007ffb`6c15fe24 : 00007ffb`65ebfb30 00000000`00a30ff2 00000000`00000096 00000000`00000001 : USER32!_fnDWORD+0x33
00000091`1fd7fcd0 00007ffb`69051164 : 00007ffb`6b14477d 00000000`00000006 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue
00000091`1fd7fd58 00007ffb`6b14477d : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14
00000091`1fd7fd60 00007ff6`5bd45176 : 00000000`00000000 00000000`00000005 00000000`00000000 00007ffb`69129f00 : USER32!GetMessageW+0x2d
00000091`1fd7fdc0 00007ff6`5bd4cf02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x5176
00000091`1fd7fed0 00007ffb`6b687bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xcf02
00000091`1fd7ff10 00007ffb`6c12cee1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
00000091`1fd7ff40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
Originally created by @jeffrson on GitHub (Oct 24, 2019). # Environment ```none Windows build number: 10.0.18362.356 Windows Terminal version: 0.5.2762 ``` # Steps to reproduce After some action (not reproducible - call stack not analyzed previously, so I don't know if it's always the same) the postmortem WinDbg is triggered. # Expected behavior No crash. # Actual behavior ``` FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_TerminalControl.dll!Unknown BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ STACK_TEXT: 00000091`1fd7f4e0 00007ffa`fff78aec : 00000285`7d213230 00000000`00000012 00000000`00000000 00007ffb`6c0ffc2c : TerminalControl+0x7ea1 00000091`1fd7f550 00007ffb`65c35ef1 : 00000000`00000000 00000285`878d6bf0 00000285`8a4ed300 00000000`00000000 : TerminalControl+0x18aec 00000091`1fd7f5a0 00007ffb`65eefba6 : 00000285`8a401d40 00000285`878d6bf0 00000285`7d0b0340 00000285`00c00040 : Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_59517943c03487243f9bea31c6c1a784>,-1>::Invoke+0x71 00000091`1fd7f5d0 00007ffb`65ebbd46 : 00000285`7d30ba80 00000285`8a4ed300 00000285`7d30ba80 00000285`8a4ed300 : CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback+0x16 00000091`1fd7f600 00007ffb`65ebae8d : 00000285`7d252ca0 00000285`7d30bcd0 00000285`8a4ed300 00000285`886f2580 : CoreMessaging!Microsoft__CoreUI__Dispatch__TimeoutHandler$CallbackThunk+0x186 00000091`1fd7f680 00007ffb`65eba818 : 00000285`886f2580 00000285`875eaa40 00000285`886f2580 00000285`7d30bb60 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch+0x2bd 00000091`1fd7f730 00007ffb`65ec1108 : 00000000`00000003 00000285`7d235d00 00000285`7d235d00 00000000`00000003 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch+0x158 00000091`1fd7f7a0 00007ffb`65ec0491 : 00000285`7d252ca0 00000091`1fd7f8d8 00000285`7d310b60 00000285`7d251bf0 : CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0xa68 00000091`1fd7f880 00007ffb`65ebfd99 : 00000285`7d251bf0 00000285`7d313220 00000000`00000000 00000000`00000000 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1d1 00000091`1fd7f970 00007ffb`65ebfbcb : 00000000`00000000 00000285`7d313220 00000000`00000000 00000000`40000c02 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_DoWork+0xe9 00000091`1fd7fa50 00007ffb`6b13681d : 00000000`00000002 00000000`80000022 00000000`00000001 00000091`1fd7fe69 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_WindowProc+0x9b 00000091`1fd7fa80 00007ffb`6b1363ec : 00000000`00008388 00007ffb`65ebfb30 00000000`000f0a18 00000000`80000000 : USER32!UserCallWinProcCheckWow+0x2bd 00000091`1fd7fc10 00007ffb`6b142d03 : 00000091`1fd7fe40 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0x9c 00000091`1fd7fc70 00007ffb`6c15fe24 : 00007ffb`65ebfb30 00000000`00a30ff2 00000000`00000096 00000000`00000001 : USER32!_fnDWORD+0x33 00000091`1fd7fcd0 00007ffb`69051164 : 00007ffb`6b14477d 00000000`00000006 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue 00000091`1fd7fd58 00007ffb`6b14477d : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14 00000091`1fd7fd60 00007ff6`5bd45176 : 00000000`00000000 00000000`00000005 00000000`00000000 00007ffb`69129f00 : USER32!GetMessageW+0x2d 00000091`1fd7fdc0 00007ff6`5bd4cf02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x5176 00000091`1fd7fed0 00007ffb`6b687bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xcf02 00000091`1fd7ff10 00007ffb`6c12cee1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14 00000091`1fd7ff40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 ```
claunia commented 2026-01-30 23:52:21 +00:00
Author
Owner
Copy Link

@jeffrson commented on GitHub (Oct 24, 2019):

In 0.6.2951 the callstack appears like this:

STACK_TEXT:  
00000038`c06fef60 00007ffb`468b8772 : 00000156`64213460 00000000`00000012 00000038`c05d8800 00007ffb`6c0ffc2c : TerminalControl+0x8268
00000038`c06fefc0 00007ffb`65c35ef1 : 00000000`00000000 00000156`6eee0b30 00000156`6f9fc280 00000000`00000000 : TerminalControl+0x18772
00000038`c06ff010 00007ffb`65eefba6 : 00000156`6f901f00 00000156`6eee0b30 00000156`64060340 00000156`00c00040 : Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_59517943c03487243f9bea31c6c1a784>,-1>::Invoke+0x71
00000038`c06ff040 00007ffb`65ebbd46 : 00000156`6430ba80 00000156`6f9fc280 00000156`6430ba80 00000156`6f9fc280 : CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback+0x16
00000038`c06ff070 00007ffb`65ebae8d : 00000156`642589d0 00000156`6430bcd0 00000156`6f9fc280 00000156`6d3812d0 : CoreMessaging!Microsoft__CoreUI__Dispatch__TimeoutHandler$CallbackThunk+0x186
00000038`c06ff0f0 00007ffb`65eba818 : 00000156`6d3812d0 00000156`6739f420 00000156`6d3812d0 00000156`6430bb60 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch+0x2bd
00000038`c06ff1a0 00007ffb`65ec1108 : 00000000`00000003 00000156`64236670 00000156`64236670 00000000`00000003 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch+0x158
00000038`c06ff210 00007ffb`65ec0491 : 00000156`642589d0 00000038`c06ff348 00000156`64310b60 00000156`64253ad0 : CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0xa68
00000038`c06ff2f0 00007ffb`65ebfd99 : 00000156`64253ad0 00000156`64313210 00000000`00000000 00000000`00000000 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1d1
00000038`c06ff3e0 00007ffb`65ebfbcb : 00000000`00000000 00000156`64313210 00000000`00000000 00000000`40000c02 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_DoWork+0xe9
00000038`c06ff4c0 00007ffb`6b13681d : 00000000`00000002 00000000`80000022 00000000`00000001 00000038`c06ff930 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_WindowProc+0x9b
00000038`c06ff4f0 00007ffb`6b1363ec : 00000000`00008388 00007ffb`65ebfb30 00000000`00120226 00000000`80000000 : USER32!UserCallWinProcCheckWow+0x2bd
00000038`c06ff680 00007ffb`6b142d03 : 00000038`c06ff8e0 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0x9c
00000038`c06ff6e0 00007ffb`6c15fe24 : 00007ffb`65ebfb30 00000002`00000030 00007ffb`69051764 00000000`00000001 : USER32!_fnDWORD+0x33
00000038`c06ff740 00007ffb`69051164 : 00007ffb`6b14477d 00000000`00000006 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue
00000038`c06ff7c8 00007ffb`6b14477d : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14
00000038`c06ff7d0 00007ff7`47c85026 : 00000000`00000000 00000000`00000000 00000000`00000000 00720065`00540073 : USER32!GetMessageW+0x2d
00000038`c06ff830 00007ff7`47c8d252 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x5026
00000038`c06ff9f0 00007ffb`6b687bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xd252
00000038`c06ffa30 00007ffb`6c12cee1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
00000038`c06ffa60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

Maybe I'll find a way to reproduce.

@jeffrson commented on GitHub (Oct 24, 2019): In 0.6.2951 the callstack appears like this: ``` STACK_TEXT: 00000038`c06fef60 00007ffb`468b8772 : 00000156`64213460 00000000`00000012 00000038`c05d8800 00007ffb`6c0ffc2c : TerminalControl+0x8268 00000038`c06fefc0 00007ffb`65c35ef1 : 00000000`00000000 00000156`6eee0b30 00000156`6f9fc280 00000000`00000000 : TerminalControl+0x18772 00000038`c06ff010 00007ffb`65eefba6 : 00000156`6f901f00 00000156`6eee0b30 00000156`64060340 00000156`00c00040 : Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_59517943c03487243f9bea31c6c1a784>,-1>::Invoke+0x71 00000038`c06ff040 00007ffb`65ebbd46 : 00000156`6430ba80 00000156`6f9fc280 00000156`6430ba80 00000156`6f9fc280 : CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback+0x16 00000038`c06ff070 00007ffb`65ebae8d : 00000156`642589d0 00000156`6430bcd0 00000156`6f9fc280 00000156`6d3812d0 : CoreMessaging!Microsoft__CoreUI__Dispatch__TimeoutHandler$CallbackThunk+0x186 00000038`c06ff0f0 00007ffb`65eba818 : 00000156`6d3812d0 00000156`6739f420 00000156`6d3812d0 00000156`6430bb60 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch+0x2bd 00000038`c06ff1a0 00007ffb`65ec1108 : 00000000`00000003 00000156`64236670 00000156`64236670 00000000`00000003 : CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch+0x158 00000038`c06ff210 00007ffb`65ec0491 : 00000156`642589d0 00000038`c06ff348 00000156`64310b60 00000156`64253ad0 : CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0xa68 00000038`c06ff2f0 00007ffb`65ebfd99 : 00000156`64253ad0 00000156`64313210 00000000`00000000 00000000`00000000 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1d1 00000038`c06ff3e0 00007ffb`65ebfbcb : 00000000`00000000 00000156`64313210 00000000`00000000 00000000`40000c02 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_DoWork+0xe9 00000038`c06ff4c0 00007ffb`6b13681d : 00000000`00000002 00000000`80000022 00000000`00000001 00000038`c06ff930 : CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter_WindowProc+0x9b 00000038`c06ff4f0 00007ffb`6b1363ec : 00000000`00008388 00007ffb`65ebfb30 00000000`00120226 00000000`80000000 : USER32!UserCallWinProcCheckWow+0x2bd 00000038`c06ff680 00007ffb`6b142d03 : 00000038`c06ff8e0 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0x9c 00000038`c06ff6e0 00007ffb`6c15fe24 : 00007ffb`65ebfb30 00000002`00000030 00007ffb`69051764 00000000`00000001 : USER32!_fnDWORD+0x33 00000038`c06ff740 00007ffb`69051164 : 00007ffb`6b14477d 00000000`00000006 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue 00000038`c06ff7c8 00007ffb`6b14477d : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14 00000038`c06ff7d0 00007ff7`47c85026 : 00000000`00000000 00000000`00000000 00000000`00000000 00720065`00540073 : USER32!GetMessageW+0x2d 00000038`c06ff830 00007ff7`47c8d252 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x5026 00000038`c06ff9f0 00007ffb`6b687bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xd252 00000038`c06ffa30 00007ffb`6c12cee1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14 00000038`c06ffa60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 ``` Maybe I'll find a way to reproduce.
claunia commented 2026-01-30 23:52:22 +00:00
Author
Owner
Copy Link

@jeffrson commented on GitHub (Oct 24, 2019):

Was trying to get information about https://github.com/microsoft/terminal/issues/3218 -

Use cmd, press return key as often as the prompt reaches the bottom. Call less <somefile>, press 'q' to close, and execute exit.

I had other crashes but I need to see if they happen again.

@jeffrson commented on GitHub (Oct 24, 2019): Was trying to get information about https://github.com/microsoft/terminal/issues/3218 - Use cmd, press `return` key as often as the prompt reaches the bottom. Call `less <somefile>`, press 'q' to close, and execute `exit`. I had other crashes but I need to see if they happen again.
claunia commented 2026-01-30 23:52:22 +00:00
Author
Owner
Copy Link

@jeffrson commented on GitHub (Oct 24, 2019):

Oh well - me again. This bug is not related to less...

Simply do something in "cmd" to move the prompt down (long dir, return a couple of times) and call exit).

@jeffrson commented on GitHub (Oct 24, 2019): Oh well - me again. This bug is not related to `less`... Simply do something in "cmd" to move the prompt down (long dir, return a couple of times) and call `exit`).
claunia commented 2026-01-30 23:52:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 24, 2019):

/feedback

@zadjii-msft commented on GitHub (Oct 24, 2019): /feedback
claunia commented 2026-01-30 23:52:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 24, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Oct 24, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and 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/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:52:22 +00:00
Author
Owner
Copy Link

@jeffrson commented on GitHub (Oct 24, 2019):

https://aka.ms/AA6dv9m

@jeffrson commented on GitHub (Oct 24, 2019): https://aka.ms/AA6dv9m
claunia commented 2026-01-30 23:52:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 29, 2019):

Interestingly, we can't get anything out of that feedback ID. Since you seem pretty handy at this, would you be willing and able to clone this repo and build/run locally to get a callstack with symbols?

Thanks!

@DHowett-MSFT commented on GitHub (Oct 29, 2019): Interestingly, we can't get anything out of that feedback ID. Since you seem pretty handy at this, would you be willing and able to clone this repo and build/run locally to get a callstack with symbols? Thanks!
claunia commented 2026-01-30 23:52:23 +00:00
Author
Owner
Copy Link

@jeffrson commented on GitHub (Oct 29, 2019):

Well, I don't know how this Feedback thingy works. Should it ask for some error to report? In fact, I don't really like that it doesn't show what exactly it sends.

Regarding a local build - as it seems, the error doesn't happen if I compile and run a debug build. However, there's a "invalid handle" exception when exiting the app:
WindowsTerminal.exe: 0xC0000008: An invalid handle was specified

In release mode, however, I get this:
image

Is this sufficient for you? And, btw, should I conclude you can't reproduce the issue?

(value is 23.00000000 if that matters)

@jeffrson commented on GitHub (Oct 29, 2019): Well, I don't know how this Feedback thingy works. Should it ask for some error to report? In fact, I don't really like that it doesn't show what exactly it sends. Regarding a local build - as it seems, the error doesn't happen if I compile and run a debug build. However, there's a "invalid handle" exception when exiting the app: WindowsTerminal.exe: 0xC0000008: An invalid handle was specified In release mode, however, I get this: ![image](https://user-images.githubusercontent.com/9551280/67812857-6eac2e80-faa0-11e9-89e5-b7982cd3a5b6.png) Is this sufficient for you? And, btw, should I conclude you can't reproduce the issue? (value is 23.00000000 if that matters)
claunia commented 2026-01-30 23:52:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 29, 2019):

This is great. Thanks! That callstack means it's a duplicate of #2947, which we must have thought was a duplicate of something else. I'll resurrect that one and move this one over.

Regarding a repro: you're right! We can't. ☹️
Feedback: Thanks for the callout here. I'll look at getting better messaging around what feedback does/is.

/dup #2947.

@DHowett-MSFT commented on GitHub (Oct 29, 2019): This is great. Thanks! That callstack means it's a duplicate of #2947, which we must have thought was a duplicate of something else. I'll resurrect that one and move this one over. Regarding a repro: you're right! We can't. ☹️ Feedback: Thanks for the callout here. I'll look at getting better messaging around what feedback does/is. /dup #2947.
claunia commented 2026-01-30 23:52:24 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 29, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 29, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Product-Terminal Resolution-Duplicate 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#4628
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?