starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal does not play well with a G-Sync enabled monitor. #8645

New Issue
Closed
opened 2026-01-31 01:34:33 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 01:34:33 +00:00
Owner
Copy Link

Originally created by @penavincent on GitHub (May 28, 2020).

Microsoft Windows [Version 10.0.19041.264]
Terminal: 1.0.1401.0

I have an Nvidia RTX3000 card and a G-sync enabled monitor that has a refresh rate of 144Hz.

When going into the Nvidia control panel and enabling G-Sync, the terminal app has horrible frame rate, causing the monitor itself to dip down to 15-20 fps, as well as the cursor and anything around it, mind you, this only happens if WindowsTerminal is the program that is focused on at the moment.

Now, there's a very easy workaround for apps with this issue, where you exclude the Gsync functionality from running from one particular app, in this case, Windows Terminal, the issue I'm having though, revolves around not being able to find the location of the Windows Terminal executable. I know it's on the \Program Files\WindowsApps folder, however, I can only see one WindowsTerminal.exe, which when opened, opens up a new Terminal with default settings, however this one doesn't suffer from the performance issue, weird.

So, where is the location of the WindowsTerminal executable that gets ran from the shortcut that you click in the start menu, for example? Nvidia control panel cannot detect the application even if it's running, which doesn't happen with any other application on my pc, even if downloaded from the MS Store as well.

I imagine it has a different method of execution? For now, I'm disabling Gsync whenever I need to use the Terminal app, but it would be nice to not have to do that, which for now, all I need is the location of WindowsTerminal in the way it gets opened from the start menu.

Thanks!

Originally created by @penavincent on GitHub (May 28, 2020). Microsoft Windows [Version 10.0.19041.264] Terminal: 1.0.1401.0 I have an Nvidia RTX3000 card and a G-sync enabled monitor that has a refresh rate of 144Hz. When going into the Nvidia control panel and enabling G-Sync, the terminal app has horrible frame rate, causing the monitor itself to dip down to 15-20 fps, as well as the cursor and anything around it, mind you, this only happens if WindowsTerminal is the program that is focused on at the moment. Now, there's a very easy workaround for apps with this issue, where you exclude the Gsync functionality from running from one particular app, in this case, Windows Terminal, the issue I'm having though, revolves around not being able to find the location of the Windows Terminal executable. I know it's on the `\Program Files\WindowsApps` folder, however, I can only see one `WindowsTerminal.exe`, which when opened, opens up a new Terminal with default settings, however this one doesn't suffer from the performance issue, weird. So, where is the location of the WindowsTerminal executable that gets ran from the shortcut that you click in the start menu, for example? Nvidia control panel cannot detect the application even if it's running, which doesn't happen with any other application on my pc, even if downloaded from the MS Store as well. I imagine it has a different method of execution? For now, I'm disabling Gsync whenever I need to use the Terminal app, but it would be nice to not have to do that, which for now, all I need is the location of WindowsTerminal in the way it gets opened from the start menu. Thanks!
claunia added the Resolution-Duplicate label 2026-01-31 01:34:33 +00:00
claunia commented 2026-01-31 01:34:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2020):

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #649 for more discussion.

/dup #649

@zadjii-msft commented on GitHub (May 28, 2020): Thanks for the suggestion! Please make sure to [search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+is%3Aopen+gsync) when filing new issues. This is already being tracked by another issue on our repo - please refer to #649 for more discussion. /dup #649
claunia commented 2026-01-31 01:34:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 28, 2020):

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!

@ghost commented on GitHub (May 28, 2020): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8645
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?