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

Renderer encountered an unexpected error: 0x887a0001 #18198

Closed
mlongtin0 opened this issue Nov 14, 2024 · 8 comments
Closed

Renderer encountered an unexpected error: 0x887a0001 #18198

mlongtin0 opened this issue Nov 14, 2024 · 8 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.

Comments

@mlongtin0
Copy link

Windows Terminal version

1.22.2912.0

Windows build number

10.0.26100.2314

Other Software

I use terminal with WSL, ssh and tmux.

Steps to reproduce

No particular steps, I get this error at random and must restart the app.

Expected Behavior

That I don't have to restart Windows Terminal unless I reboot Windows.

Actual Behavior

I get this error at random and must restart the app.
This can happen after 15 minutes or after two weeks of running. It happens a few times per month. I use the windows terminal constantly.

Image

@mlongtin0 mlongtin0 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 Nov 14, 2024
@DHowett
Copy link
Member

DHowett commented Nov 14, 2024

What happens after you dismiss the warning dialog? If you resize the window after dismissing it, does it start working again?

@mlongtin0
Copy link
Author

I comes back almost immediately until I restart. I didn't try resizing, I usually run at full screen.

@Kamol7520

This comment has been minimized.

@lhecker
Copy link
Member

lhecker commented Nov 15, 2024

If it happens this rarely it'll be very difficult to diagnose this, because most debugging tools that would apply here are meant to be run only for brief periods.
As an initial attempt, I'd recommend making sure that all your drivers are up to date, in particular your GPU driver. In case of GPU drivers specifically, I strongly recommend against relying on your manufacturer's website for updates and would instead go to the AMD/Intel/Nvidia driver download site directly.
If you're using "hybrid graphics" like with a laptop, it may worth trying to switch to your other GPU as described in this fairly similar issue: #15601 (comment)

@mlongtin0
Copy link
Author

Straight corporate laptop with intel graphics. Everything else about it works fine.

Is there anything I could do to get a stack trace or something more helpful?

@lhecker
Copy link
Member

lhecker commented Nov 15, 2024

Is there anything I could do to get a stack trace or something more helpful?

That's the problem... Outside of attaching a debugger before the issue occurs it's difficult to capture the moment and corresponding output.

@mlongtin0
Copy link
Author

If I zoom in or out (change font size), after the initial error, the error does not come back immediately.

If I don't do anything, the error re-appears after a few seconds. I guess I could attach a debugger at that point or enable some really verbose logging.

@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 Nov 20, 2024
@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 Nov 24, 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.

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.
Projects
None yet
Development

No branches or pull requests

5 participants