Skip to content
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

Terminal crashes when I click on the mark point. #17836

Closed
markox92 opened this issue Aug 30, 2024 · 3 comments
Closed

Terminal crashes when I click on the mark point. #17836

markox92 opened this issue Aug 30, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Product-Terminal The new Windows Terminal. Severity-Crash Crashes are real bad news.

Comments

@markox92
Copy link

markox92 commented Aug 30, 2024

Windows Terminal version

1.21.2361.0

Windows build number

22631.4112

Other Software

No response

Steps to reproduce

I'm watching some realtime logs from a Python app; after a few minutes, when I click on the mark point, the terminal crashes.

Another problem with this last version is that when you have very long output and scroll up, then when I press the keyboard's up or down to run a command again, the terminal won't go to the current command, it stays in the same position, and I must scroll down to check what I have as a prompt. This wasn't happened before

Expected Behavior

No response

Actual Behavior

Only what i can found in event logs is this

Faulting application name: WindowsTerminal.exe, version: 1.21.2408.23001, time stamp: 0x66c8f3fe
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.4111, time stamp: 0x66b5fe39
Exception code: 0xc000027b
Fault offset: 0x000000000086fb40
Faulting process id: 0x0x1850
Faulting application start time: 0x0x1DAFB0FA150B7FB
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.2361.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: a43ed049-a3b0-4e94-b9fb-5a17d8a14aa0
Faulting package full name: Microsoft.WindowsTerminal_1.21.2361.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@markox92 markox92 added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 30, 2024
@zadjii-msft
Copy link
Member

Could you try reproing this crash with the Feedback Hub's problem recorder? If you share the link to the /feedback here, we should be able to find the crash dump in the backend. Thanks!

@zadjii-msft zadjii-msft added the Severity-Crash Crashes are real bad news. label Sep 3, 2024
Copy link
Contributor

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

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Sep 3, 2024
@zadjii-msft zadjii-msft added Product-Terminal The new Windows Terminal. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Sep 3, 2024
@carlos-zamora carlos-zamora added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Sep 4, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Product-Terminal The new Windows Terminal. Severity-Crash Crashes are real bad news.
Projects
None yet
Development

No branches or pull requests

3 participants