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

random artifacts when using opengl with intel iris xe graphics on windows #4992

Open
andysbolton opened this issue Feb 10, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@andysbolton
Copy link

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

When WezTerm is in a small window, I see a lot of flickering, particularly when typing, clicking, and resizing. I haven't tested this on nightly, but it is happening on the current and two previous stable releases.
This issue doesn't seem to happen at all when the window is docked or maximized.

wezterm

To Reproduce

Unfortunately, I'm not sure of the best way to reproduce this. I haven't seen it happen on my previous computer, only on a new Lenovo ThinkPad.

winfetch

Configuration

No config

Expected Behavior

No response

Logs

No logs were outputted during the flickering.

Anything else?

No response

@andysbolton andysbolton added the bug Something isn't working label Feb 10, 2024
@vvvvv
Copy link

vvvvv commented Feb 11, 2024

Could you please retest on nightly?

Disclaimer: I know nothing about windows and stumbled over this issue by accident.

This looks like a TTY issue to me.
Do you use any OSC escape sequences by any chance?
If so try disabling them by setting WEZTERM_SHELL_SKIP_ALL=1.

Maybe related to microsoft/terminal#12336.

@andysbolton
Copy link
Author

I was having trouble testing nightly because of org security settings but was able to get it working via Scoop, unfortunately the issue seems to persist:
wezterm2

I'm not using any OSC escape sequences at the moment, and FWIW setting WEZTERM_SHELL_SKIP_ALL=1 doesn't seem to have an effect.

@wez
Copy link
Owner

wez commented Feb 11, 2024

Those artifacts look like junk data in a texture that is mapped into the GPU
I've never seen that happen in wezterm before, so I'm suspicious of this being related to the OpenGL or other graphics drivers on that system. Perhaps a buffer is being presented before it is ready? Or perhaps there is some kind of (honestly very scary!) memory corruption issue?

I'd suggest looking at changing the front_end and see if things improve:
https://wezfurlong.org/wezterm/config/lua/config/front_end.html

You can see which is in use by pressing CTRL-SHIFT-L to get into the debug overlay (please share that before you make any config changes).

If you're on OpenGL try switching to webgpu. If you're on webpu try switching to OpenGL, and/or experimenting with other webgpu adapater choices: https://wezfurlong.org/wezterm/config/lua/config/webgpu_preferred_adapter.html

@wez wez added the waiting-on-op Waiting for more information from the original poster label Feb 11, 2024
@andysbolton
Copy link
Author

Thank you @wez, setting it to WebGpu resolves it, will leave it on that.
webgpu
FYI with no config or explicitly set to OpenGL or Software it looks like the artifacts appear, here it is with no config:
default

@github-actions github-actions bot removed the waiting-on-op Waiting for more information from the original poster label Feb 11, 2024
@wez
Copy link
Owner

wez commented Feb 11, 2024

I'm leaning towards calling this a bug in the intel iris/xe opengl implementation on that system

@wez wez changed the title Screen flickering and splotchiness when WezTerm is not maximized or docked random artifacts when using opengl with intel iris xe graphics on windows Feb 11, 2024
@danct9a
Copy link

danct9a commented Feb 15, 2024

Adding this to confirm it's not an isolated case.

I also experienced a similar issue in Windows 11. I have a Intel(R) Iris(R) Xe Graphics (8086:A7A1) iGPU, and config.front_end was also set to OpenGL.

Since changing to WebGpu, my issue is also resolved. Thanks wez!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants