Having terminal open causes 3D applications to stutter

[Masamune3210]

Windows Terminal version

1.16.3464.0

Windows build number

Microsoft Windows [Version 10.0.22621.963]

Other Software

AMD Graphics Driver ver 22.11.2? I'm not sure who to blame here, Terminal, AMD, or both

Steps to reproduce

Play a game or do any 3D rendering that is taxing

Expected Behavior

No Stutter

Actual Behavior

Stutter, seemingly linked up with any time Terminal refreshes its window contents

[Masamune3210]

Like I said in the main message, I am not sure who to blame here. I don't know if AMD has a swap issue in their driver when multiple applications are using acceleration at a time, or if Terminal has the blame due to some inefficiency in something like message handling or being too hasty when handling redraw

[Masamune3210]

Issue only seems to occur if Terminal currently is rapidly updating its window contents, having a blank command prompt window open is fine, but running something like rclone in verbose mode and having it spit out stuff causes the stutter to appear

[lhecker]

Are you perhaps using a display with variable refresh rate?

[Masamune3210]

Yes, but on the other monitor, terminal on one monitor, the game on another monitor. Both supporting FreeSync

[lhecker]

Just to be sure, this issue happens with any 3D application for you right?
Does the issue still happen if neither monitor is actively using VRR/FreeSync?

Do you have this setting enabled?

[Masamune3210]

I havent tried with FreeSync off, let me check

[Masamune3210]

I do not seem to get the issue with FreeSync disabled

[zadjii-msft]

Sounds to me like this is #649?

[Masamune3210]

Looks to be the case, sorry for not searching for dups. My only alternate to the existing issue is having a Terminal window that isn't changing (i.e. a blank Command Prompt window) actually allows things to run at the correct refresh rate, since the blinking cursor only draws when the Terminal is focused

[zadjii-msft]

No worries, /dup #649

[ghost]

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!