Renderer encountered an unexpected error: 0x887a0001

[mlongtin0]

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.

[DHowett]

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

[mlongtin0]

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

[lhecker]

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]

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]

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]

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.