starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Extremely sluggish behavior when in full screen on a 4K monitor #4911

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

Originally created by @basavyr on GitHub (Nov 11, 2019).

Environment

Windows build number:
Platform      Version               VersionString
Win32NT     10.0.18362.0        Microsoft Windows NT 10.0.18362.0
Windows Terminal version: Version: 0.6.2951.0

Steps to reproduce

Make the Windows Terminal go full-screen on a 4K monitor.

Expected behavior

Fast and responsive (like it performs in non-full screen mode).

Actual behavior

Super slow and sluggish behavior. There is at least a 2s delay for typing and using ls for example will result in a slow animation for listing the content in a directory. The Terminal is pretty much unusable if I go full-screen

I have a laptop with a 1080p display and I also have an external monitor connected via mini-display port. Monitor is 4K native 60 Hz, and it works without any issues. My laptop has also a dedicated GPU (nVidia GTX850m with the latest drivers). All other apps (i.e. Spotify, Microsoft Edge, Word etc) perform just fine when in full-screen on this 4K display. However, the Windows Terminal performs super slow when I go full screen on the monitor.
Terminal performs fine when I put it in full-screen on the laptop's main display.

Originally created by @basavyr on GitHub (Nov 11, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Platform Version VersionString Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version: Version: 0.6.2951.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Make the Windows Terminal go full-screen on a 4K monitor. # Expected behavior Fast and responsive (like it performs in non-full screen mode). <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Super slow and sluggish behavior. There is at least a 2s delay for typing and using `ls` for example will result in a slow animation for listing the content in a directory. The Terminal is pretty much unusable if I go full-screen <!-- What's actually happening? --> I have a laptop with a 1080p display and I also have an external monitor connected via mini-display port. Monitor is 4K native 60 Hz, and it works without any issues. My laptop has also a dedicated GPU (nVidia GTX850m with the latest drivers). All other apps (i.e. Spotify, Microsoft Edge, Word etc) perform just fine when in full-screen on this 4K display. However, the Windows Terminal performs super slow when I go full screen on the monitor. Terminal performs fine when I put it in full-screen on the laptop's main display.
claunia commented 2026-01-31 00:00:04 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Nov 11, 2019):

Oh 4K display. That's probably where #778 come in handy. I've never tried Windows Terminal on 4K display yet.

@skyline75489 commented on GitHub (Nov 11, 2019): Oh 4K display. That's probably where #778 come in handy. I've never tried Windows Terminal on 4K display yet.
claunia commented 2026-01-31 00:00:05 +00:00
Author
Owner
Copy Link

@basavyr commented on GitHub (Nov 11, 2019):

Thank you for responding to this :)
Regarding the #778 issue, I have some trouble understanding what do I have to change. I've only tried turning off acrylic, but that didn't help at all.

@basavyr commented on GitHub (Nov 11, 2019): Thank you for responding to this :) Regarding the #778 issue, I have some trouble understanding what do I have to change. I've only tried turning off acrylic, but that didn't help at all.
claunia commented 2026-01-31 00:00:05 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 11, 2019):

Do you know how to get a WPR trace of it? @skyline75489 might be able to help you get one. It would be interesting to see if it's something we're doing or outside our control (and we can get it into the right team's hands.)

@miniksa commented on GitHub (Nov 11, 2019): Do you know how to get a WPR trace of it? @skyline75489 might be able to help you get one. It would be interesting to see if it's something we're doing or outside our control (and we can get it into the right team's hands.)
claunia commented 2026-01-31 00:00:07 +00:00
Author
Owner
Copy Link

@basavyr commented on GitHub (Nov 12, 2019):

@miniksa I got one WPR trace. Never tried it before, but I checked the documentation on Microsoft's website and I think I've managed to record the performance of this app. I hope it helps: I only had Windows Terminal as the running app on my desktop. I did put it in full screen mode and I start to type a bit inside the terminal, after that I just stopped the performance analyzer.

Trace file can be found here:
Firefox Send link
Please let me know if everything is ok!
Cheers :)

Btw, Firefox Send keeps the file available to download only for 7 days, so let me know if you can't access the file.

@basavyr commented on GitHub (Nov 12, 2019): @miniksa I got one WPR trace. Never tried it before, but I checked the documentation on Microsoft's website and I think I've managed to record the performance of this app. I hope it helps: I only had Windows Terminal as the running app on my desktop. I did put it in full screen mode and I start to type a bit inside the terminal, after that I just stopped the performance analyzer. Trace file can be found here: [Firefox Send link](https://send.firefox.com/download/f21c2c4a2cbd1d36/#VImGNb6S7ZldsYL9ptKKng) Please let me know if everything is ok! Cheers :) Btw, Firefox Send keeps the file available to download only for 7 days, so let me know if you can't access the file.
claunia commented 2026-01-31 00:00:08 +00:00
Author
Owner
Copy Link

@ashao commented on GitHub (Jan 22, 2020):

Just to an interesting symptom to this conversation as someone who's also using a 4K monitor hooked up to a laptop:
If I split the panes, the response noticeably improves. Splitting into 4 equal panes gives me the same (fast) response as being on my native laptop display.

@ashao commented on GitHub (Jan 22, 2020): Just to an interesting symptom to this conversation as someone who's also using a 4K monitor hooked up to a laptop: If I split the panes, the response noticeably improves. Splitting into 4 equal panes gives me the same (fast) response as being on my native laptop display.
claunia commented 2026-01-31 00:00:10 +00:00
Author
Owner
Copy Link

@Jewsh-S commented on GitHub (Mar 12, 2020):

I wanted to put a confirmation on this and I believe it is tied to 778. This isn't just 4k, but general size of the app window. If I make the app very very small, I get some what decent performance, but the bigger I make the app, the the worse the performance gets. At 4k full screen, I get about 1.5 second of lag after I press a key until it actually outputs to the app window. My first thought was that this might be my PC, because I normally force my laptop to disable the high performance GPU. However, i force enabled my high performance GPU and the performance stayed the exact same. This is definitely a drawing issue that makes the app almost unusable as the number of pixels that the terminal is using increases.

@Jewsh-S commented on GitHub (Mar 12, 2020): I wanted to put a confirmation on this and I believe it is tied to [778](https://github.com/microsoft/terminal/issues/778). This isn't just 4k, but general size of the app window. If I make the app very very small, I get some what decent performance, but the bigger I make the app, the the worse the performance gets. At 4k full screen, I get about 1.5 second of lag after I press a key until it actually outputs to the app window. My first thought was that this might be my PC, because I normally force my laptop to disable the high performance GPU. However, i force enabled my high performance GPU and the performance stayed the exact same. This is definitely a drawing issue that makes the app almost unusable as the number of pixels that the terminal is using increases.
claunia commented 2026-01-31 00:00:11 +00:00
Author
Owner
Copy Link

@florianheinemann commented on GitHub (Mar 25, 2020):

This isn't just 4k, but general size of the app window. If I make the app very very small, I get some what decent performance, but the bigger I make the app, the the worse the performance gets. At 4k full screen, I get about 1.5 second of lag after I press a key until it actually outputs to the app window.

I have the exact same observation. Performance gets exponentially worse with every bit I increase the size of the window. On 4k it is basically unusable

@florianheinemann commented on GitHub (Mar 25, 2020): > > > This isn't just 4k, but general size of the app window. If I make the app very very small, I get some what decent performance, but the bigger I make the app, the the worse the performance gets. At 4k full screen, I get about 1.5 second of lag after I press a key until it actually outputs to the app window. I have the exact same observation. Performance gets exponentially worse with every bit I increase the size of the window. On 4k it is basically unusable
claunia commented 2026-01-31 00:00:12 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Apr 15, 2020):

@DHowett-MSFT, this is another one we're not going to be able to land.

@miniksa commented on GitHub (Apr 15, 2020): @DHowett-MSFT, this is another one we're not going to be able to land.
claunia commented 2026-01-31 00:00:13 +00:00
Author
Owner
Copy Link

@AH-Merii commented on GitHub (Apr 28, 2020):

I still have the exact same issue after updating to the latest version 0.11.1121.0 .

When running the terminal in full-screen on a 4k monitor, typing becomes sluggish. Sluggishness is directly proportional to window size, as window size increases so does the sluggishness.

Toggling acrylic off seems to improve the performance but not by much. Note: this is not an issue on when using the legacy cmd/powershell terminal.

@AH-Merii commented on GitHub (Apr 28, 2020): I still have the exact same issue after updating to the latest version 0.11.1121.0 . When running the terminal in full-screen on a 4k monitor, typing becomes sluggish. Sluggishness is directly proportional to window size, as window size increases so does the sluggishness. Toggling acrylic off seems to improve the performance but not by much. Note: this is not an issue on when using the legacy cmd/powershell terminal.
claunia commented 2026-01-31 00:00:14 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 28, 2020):

Thanks for the corroborating report. This should be resolved when #5345 is in a released build.

@DHowett-MSFT commented on GitHub (Apr 28, 2020): Thanks for the corroborating report. This should be resolved when #5345 is in a released build.
claunia commented 2026-01-31 00:00:15 +00:00
Author
Owner
Copy Link

@basavyr commented on GitHub (Apr 28, 2020):

Awesome! Great job!

@basavyr commented on GitHub (Apr 28, 2020): Awesome! Great job!
claunia commented 2026-01-31 00:00:15 +00:00
Author
Owner
Copy Link

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

:tada:This issue was addressed in #5345, which has now been successfully released as Windows Terminal Release Candidate v0.11.1251.0 (1.0rc1).🎉

Handy links:

@ghost commented on GitHub (May 5, 2020): :tada:This issue was addressed in #5345, which has now been successfully released as `Windows Terminal Release Candidate v0.11.1251.0 (1.0rc1)`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.11.1251.0 (1.0rc1)) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 00:00:16 +00:00
Author
Owner
Copy Link

@AH-Merii commented on GitHub (May 6, 2020):

Thanks for the corroborating report. This should be resolved when #5345 is in a released build.

Hey, I just downloaded the new version, which was supposed to address this issue, I just wanted to report that I am still encountering the same problem regarding the sluggish typing experience. Unfortunately, all the same observations that I mentioned in my above comment still apply.

@AH-Merii commented on GitHub (May 6, 2020): > Thanks for the corroborating report. This should be resolved when #5345 is in a released build. Hey, I just downloaded the new version, which was supposed to address this issue, I just wanted to report that I am still encountering the same problem regarding the sluggish typing experience. Unfortunately, all the same observations that I mentioned in my above comment still apply.
claunia commented 2026-01-31 00:00:17 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

Reopening this one, but moving out of the 1.0 milestone. Sorry about that!

@DHowett-MSFT commented on GitHub (May 7, 2020): Reopening this one, but moving out of the 1.0 milestone. Sorry about that!
claunia commented 2026-01-31 00:00:18 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

@basavyr does it work better for you?

@DHowett-MSFT commented on GitHub (May 7, 2020): @basavyr does it work better for you?
claunia commented 2026-01-31 00:00:20 +00:00
Author
Owner
Copy Link

@basavyr commented on GitHub (May 7, 2020):

Hey there @DHowett-MSFT. Thank you for still continuing to work on this issue which I've encountered a while back.
Unfortunately, I can't provide any feedback, as for the last couple of months, I've switched entirely to macOS. As a result, I have no more Windows devices, so I am not able to test that.
I hope others can give feedback on this issue.

Best regards!

@basavyr commented on GitHub (May 7, 2020): Hey there @DHowett-MSFT. Thank you for still continuing to work on this issue which I've encountered a while back. Unfortunately, I can't provide any feedback, as for the last couple of months, I've switched entirely to _macOS_. As a result, I have no more Windows devices, so I am not able to test that. I hope others can give feedback on this issue. Best regards!
claunia commented 2026-01-31 00:00:21 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (May 17, 2020):

So I've finally got a 4K moniter and I still can not reproduce this. I've tried 100% and 200% scale. The performance is not very so bad to me. I don't feel there's significant difference in performance between 4K and 1080p. I wonder if there's something that's missing. Is it the graphic card of something? I'm using RX570 + Dell P2715Q.

@skyline75489 commented on GitHub (May 17, 2020): So I've finally got a 4K moniter and I still can not reproduce this. I've tried 100% and 200% scale. The performance is not very so bad to me. I don't feel there's significant difference in performance between 4K and 1080p. I wonder if there's something that's missing. Is it the graphic card of something? I'm using RX570 + Dell P2715Q.
claunia commented 2026-01-31 00:00:22 +00:00
Author
Owner
Copy Link

@AH-Merii commented on GitHub (May 18, 2020):

So I've finally got a 4K moniter and I still can not reproduce this. I've tried 100% and 200% scale. The performance is not very so bad to me. I don't feel there's significant difference in performance between 4K and 1080p. I wonder if there's something that's missing. Is it the graphic card of something? I'm using RX570 + Dell P2715Q.

I have noticed a significant improvement after the update. However, the problem persists when activating acrylic mode. I don't think it's a problem with the graphics card because when I use powershell with decreased opacity it's performance remains the same.

TLDR:

  • Performance has significantly improved however it can still be improved further to be on par with CMD/Powershell.
  • Problem still persists when using Acrylic mode.
@AH-Merii commented on GitHub (May 18, 2020): > So I've finally got a 4K moniter and I still can not reproduce this. I've tried 100% and 200% scale. The performance is not very so bad to me. I don't feel there's significant difference in performance between 4K and 1080p. I wonder if there's something that's missing. Is it the graphic card of something? I'm using RX570 + Dell P2715Q. I have noticed a significant improvement after the update. However, the problem persists when activating acrylic mode. I don't think it's a problem with the graphics card because when I use powershell with decreased opacity it's performance remains the same. TLDR: - Performance has significantly improved however it can still be improved further to be on par with CMD/Powershell. - Problem still persists when using Acrylic mode.
claunia commented 2026-01-31 00:00:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 19, 2020):

Those of you who are still seeing this problem WITH ACRYLIC OFF

What software are you using inside Terminal? Tmux? Screen? WSL? PowerShell? Anything?

@DHowett commented on GitHub (May 19, 2020): Those of you who _are_ still seeing this problem **WITH ACRYLIC OFF** What software are you using inside Terminal? Tmux? Screen? WSL? PowerShell? Anything?
claunia commented 2026-01-31 00:00:23 +00:00
Author
Owner
Copy Link

@AH-Merii commented on GitHub (May 19, 2020):

Sorry for not being specific enough but it's really odd. I tried using it with WSL, CMD, & Powershell, all their performance is comparable with each other, their performance is acceptable and much better than before.However, I am sure that performance slows down as I use it, I will try and test it extensively over the weekend, with acrylic off, so that I can reliably reproduce the issue.

@AH-Merii commented on GitHub (May 19, 2020): Sorry for not being specific enough but it's really odd. I tried using it with WSL, CMD, & Powershell, all their performance is comparable with each other, their performance is acceptable and much better than before.However, I am sure that performance slows down as I use it, I will try and test it extensively over the weekend, with acrylic off, so that I can reliably reproduce the issue.
claunia commented 2026-01-31 00:00:24 +00:00
Author
Owner
Copy Link

@ashao commented on GitHub (May 21, 2020):

The performance on my machine is great after the update to v1.0.1401.0. Both the native Powershell and Powershell within Windows Terminal (with and without Acrylic.) have the same responsiveness

This is on a Dell Precision M5510 with a Quadro M1000M.

@ashao commented on GitHub (May 21, 2020): The performance on my machine is great after the update to v1.0.1401.0. Both the native Powershell and Powershell within Windows Terminal (with and without Acrylic.) have the same responsiveness This is on a Dell Precision M5510 with a Quadro M1000M.
claunia commented 2026-01-31 00:00:25 +00:00
Author
Owner
Copy Link

@BaconTentacles commented on GitHub (Jun 23, 2020):

Those of you who are still seeing this problem WITH ACRYLIC OFF

What software are you using inside Terminal? Tmux? Screen? WSL? PowerShell? Anything?

Anything and everything. PowerShell 5, PowerShell 7, Git Bash, cmd.exe, you name it. Version 1.0.1401.0

Lenovo Legion Y740-15IRHg - nVidia GeForce RTX 2060 - 1080p laptop monitor. Window is very slow to come up, and typing is absolutely painful. It's basically unusable in this state, which is a shame, because I love it on my work PC (Dell Precision 5530).

EDIT - I take that back. PC was exhibiting some strange behavior all around, so I rebooted. Now it's running along fine. Weeeeeird. The RTX does do some strange things with certain apps (can't use Snagit, because it tries to use max 4k resolution and then scale down do 1080p, which works for Skyrim, but not so much for Snagit).

So...false alarm.

@BaconTentacles commented on GitHub (Jun 23, 2020): > Those of you who _are_ still seeing this problem **WITH ACRYLIC OFF** > > What software are you using inside Terminal? Tmux? Screen? WSL? PowerShell? Anything? Anything and everything. PowerShell 5, PowerShell 7, Git Bash, cmd.exe, you name it. Version 1.0.1401.0 Lenovo Legion Y740-15IRHg - nVidia GeForce RTX 2060 - 1080p laptop monitor. Window is very slow to come up, and typing is absolutely painful. It's basically unusable in this state, which is a shame, because I love it on my work PC (Dell Precision 5530). EDIT - I take that back. PC was exhibiting some strange behavior all around, so I rebooted. Now it's running along fine. Weeeeeird. The RTX does do some strange things with certain apps (can't use Snagit, because it tries to use max 4k resolution and then scale down do 1080p, which works for Skyrim, but not so much for Snagit). So...false alarm.
claunia commented 2026-01-31 00:00:26 +00:00
Author
Owner
Copy Link

@noomz commented on GitHub (Dec 15, 2020):

I also have this issue with Acrylic turn on.

PC: Lenovo P1 gen 3
Graphics card: Intel integrated graphic card / Quadro T1000 max-q
Monitor: Internal display (4K, 225% zoom) / LG 27UL600-W (4K, 150% zoom)

Windows: 10 Pro 10.0.19042 Build 19042
GPU Driver: Lenovo NVIDIA Driver 27.21.14.5256 (14 Dec 2020)

Symptoms: When Window Terminal is on the external monitor, it works fine. But lag movement with the internal display. GPU 1 (Quadro) is used. The weird is that when the terminal window is halfway between 2 monitors (mainly on external, LG) it doesn't lag.

@noomz commented on GitHub (Dec 15, 2020): I also have this issue with Acrylic turn on. PC: Lenovo P1 gen 3 Graphics card: Intel integrated graphic card / Quadro T1000 max-q Monitor: Internal display (4K, 225% zoom) / LG 27UL600-W (4K, 150% zoom) Windows: 10 Pro 10.0.19042 Build 19042 GPU Driver: Lenovo NVIDIA Driver 27.21.14.5256 (14 Dec 2020) Symptoms: When Window Terminal is on the external monitor, it works fine. But lag movement with the internal display. GPU 1 (Quadro) is used. The weird is that when the terminal window is halfway between 2 monitors (mainly on external, LG) it doesn't lag.
claunia commented 2026-01-31 00:00:27 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Jan 1, 2021):

Extremly sluggish behaviour here too on a Desktop triple monitor system (with Windows terminal opened only on one monitor). Typing each letter of a command at the prompt has about a 0.5 to 2 sec delay. Resizing the Terminal (to be smaller) does not make it faster.

I'm on a 3 monitor setup (each only 1680x1050), in independent mode (without Nvidia Surround enabled). I haven't turned on Acrylic (as far as I know .. I'm unclear what Acrylic is ... but I don't have "Acrylic" anywhere in my Windows Terminal Settings file). Tried within Windows Terminal for: Powershell 7.1.0, Powerhsell 5.

(On my separate laptop system Windows Terminal works just fine).

WIndows Teriminal Version: 1.4.3243.0

Windows:

Edition:      Windows 10 Pro
Version:      20H2
OS build:     19042.685

Nvidia Drivers:

451.67 (Game Ready Driver)

System:

Operating System
  Windows 10 Pro 64-bit
CPU
  Intel Core i7 3770 @ 3.40GHz  44°C
  Ivy Bridge 22nm Technology
RAM
  8.00GB Dual-Channel DDR3 @ 788MHz (9-9-9-24)
Motherboard
  Intel Corporation DZ77GA-70K (CPU 1)  32°C
Graphics
  VX2262wm (1680x1050@59Hz)
  VX2262wm (1680x1050@59Hz)
  VX2262wm (1680x1050@59Hz)
  2047MB NVIDIA GeForce GTX 1660 Ti (ASUStek Computer Inc)  31°C
Storage
  1863GB Western Digital WDC WD20NPVZ-00WFZT0 (SATA )  30°C
  953GB Samsung SSD 850 PRO 1TB (SATA (SSD))  34°C
Optical Drives
  No optical disk drives detected
Audio
  Realtek High Definition Audio

Edit 2021-01-28: I see now what "Acrylic" is: https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#acrylic-settings. As mentioned I do not have "useAcrylic" anywhere in my WT settings. So, indeed, I'm not using Acrylic and I'm getting the sluggishness.

@JohnLukeBentley commented on GitHub (Jan 1, 2021): Extremly sluggish behaviour here too on a Desktop triple monitor system (with Windows terminal opened only on one monitor). Typing each letter of a command at the prompt has about a 0.5 to 2 sec delay. Resizing the Terminal (to be smaller) does not make it faster. I'm on a 3 monitor setup (each only 1680x1050), in independent mode (without Nvidia Surround enabled). I haven't turned on Acrylic (as far as I know .. I'm unclear what Acrylic is ... but I don't have "Acrylic" anywhere in my Windows Terminal Settings file). Tried within Windows Terminal for: Powershell 7.1.0, Powerhsell 5. (On my separate laptop system Windows Terminal works just fine). WIndows Teriminal Version: 1.4.3243.0 Windows: Edition: Windows 10 Pro Version: 20H2 OS build: 19042.685 Nvidia Drivers: 451.67 (Game Ready Driver) System: Operating System Windows 10 Pro 64-bit CPU Intel Core i7 3770 @ 3.40GHz 44°C Ivy Bridge 22nm Technology RAM 8.00GB Dual-Channel DDR3 @ 788MHz (9-9-9-24) Motherboard Intel Corporation DZ77GA-70K (CPU 1) 32°C Graphics VX2262wm (1680x1050@59Hz) VX2262wm (1680x1050@59Hz) VX2262wm (1680x1050@59Hz) 2047MB NVIDIA GeForce GTX 1660 Ti (ASUStek Computer Inc) 31°C Storage 1863GB Western Digital WDC WD20NPVZ-00WFZT0 (SATA ) 30°C 953GB Samsung SSD 850 PRO 1TB (SATA (SSD)) 34°C Optical Drives No optical disk drives detected Audio Realtek High Definition Audio Edit 2021-01-28: I see now what "Acrylic" is: https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#acrylic-settings. As mentioned I do not have "useAcrylic" anywhere in my WT settings. So, indeed, I'm not using Acrylic and I'm getting the sluggishness.
claunia commented 2026-01-31 00:00:28 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Jan 24, 2021):

It's not clear if #7710 isn't the same issue.

@JohnLukeBentley commented on GitHub (Jan 24, 2021): It's not clear if #7710 isn't the same issue.
claunia commented 2026-01-31 00:00:28 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Jan 30, 2021):

I've removed my extreme sluggishness in WT by unintalling Powershell (core) 64bit, and installing Powershell (core) 32 bit. E.g. https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/PowerShell-7.1.1-win-x86.msi

Can anyone else remove their sluggishness by doing the same?

@JohnLukeBentley commented on GitHub (Jan 30, 2021): I've removed my extreme sluggishness in WT by unintalling Powershell (core) 64bit, and installing Powershell (core) 32 bit. E.g. https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/PowerShell-7.1.1-win-x86.msi Can anyone else remove their sluggishness by doing the same?
claunia commented 2026-01-31 00:00:29 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Feb 6, 2021):

Alas the update of Windows Terminal (automatically through the store) to 1.5.10271.0 has made the sluggishness return, with Powershell 32 bit installed.

@JohnLukeBentley commented on GitHub (Feb 6, 2021): Alas the update of Windows Terminal (automatically through the store) to 1.5.10271.0 has made the sluggishness return, with Powershell 32 bit installed.
claunia commented 2026-01-31 00:00:29 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 10, 2022):

FYI: In my experience this issue is fixed by enabling the new AtlasEngine:

  • Install Windows Terminal Preview 1.13
  • Either
    • Select "Enable experimental text rendering engine" in the advanced settings of your default profile, or
    • Add "experimental.useAtlasEngine": true to your profile "default" object in your settings.json
  • Restart Windows Terminal

On my 4K 120Hz display, selections, scrolling, drawing all occur at a stable, fluent 120 FPS and I couldn't observe any lags myself. I'd be extremely awesome if anyone else in this issue could confirm whether this new rendering engine still feels laggy or not. 🙂

A warning though: The current Nvidia drivers have a bug where "AtlasEngine" is recognized as an application that wants G-Sync which leads to the desktop stuttering randomly. The only proper solution seems to disable G-Sync unfortunately. We've contacted Nvidia about this already.

@lhecker commented on GitHub (Feb 10, 2022): FYI: In my experience this issue is fixed [by enabling the new AtlasEngine](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-13-release/#new-rendering-engine): * Install Windows Terminal Preview 1.13 * Either * Select "Enable experimental text rendering engine" in the advanced settings of your default profile, or * Add `"experimental.useAtlasEngine": true` to your profile `"default"` object in your `settings.json` * Restart Windows Terminal On my 4K 120Hz display, selections, scrolling, drawing all occur at a stable, fluent 120 FPS and I couldn't observe any lags myself. I'd be extremely awesome if anyone else in this issue could confirm whether this new rendering engine still feels laggy or not. 🙂 A warning though: The current Nvidia drivers have a bug where "AtlasEngine" is recognized as an application that wants G-Sync which leads to the desktop stuttering randomly. The only proper solution seems to disable G-Sync unfortunately. We've contacted Nvidia about this already.
claunia commented 2026-01-31 00:00:30 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 3, 2023):

I'll go ahead and close this issue for now. I'm fairly confident that "AtlasEngine" fixes the issue as mentioned above. You can now easily enable it in the "Rendering" settings, if it isn't enabled already.

@lhecker commented on GitHub (May 3, 2023): I'll go ahead and close this issue for now. I'm fairly confident that "AtlasEngine" fixes the issue as mentioned above. You can now easily enable it in the "Rendering" settings, if it isn't enabled already.
claunia commented 2026-01-31 00:00:30 +00:00
Author
Owner
Copy Link

@Fish1 commented on GitHub (Jun 7, 2023):

Switching to software rendering seemed to fix this issue for me.

@Fish1 commented on GitHub (Jun 7, 2023): Switching to software rendering seemed to fix this issue for me.
claunia commented 2026-01-31 00:00:31 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 7, 2023):

@Fish1 Do you have a Nvidia GPU?

@lhecker commented on GitHub (Jun 7, 2023): @Fish1 Do you have a Nvidia GPU?
claunia commented 2026-01-31 00:00:32 +00:00
Author
Owner
Copy Link

@Fish1 commented on GitHub (Jun 7, 2023):

Nah AMD graphics.

I just noticed, windows did an auto update and replaced my latest driver with something they decided...

I am going to guess that is the issue, because yesterday I had the latest drivers from AMD (via AMD adrenaline) and everything was fine. I'll fix my drivers to verify.

image

@Fish1 commented on GitHub (Jun 7, 2023): Nah AMD graphics. I just noticed, windows did an auto update and replaced my latest driver with something they decided... I am going to guess that is the issue, because yesterday I had the latest drivers from AMD (via AMD adrenaline) and everything was fine. I'll fix my drivers to verify. ![image](https://github.com/microsoft/terminal/assets/13600696/6af0db43-99b1-475b-96fd-e4bcce7c3b41)
claunia commented 2026-01-31 00:00:32 +00:00
Author
Owner
Copy Link

@Fish1 commented on GitHub (Jun 7, 2023):

No luck with reinstalling my drivers from AMD.

If I hold down a key for a second, the inputs start to lag. The only option that seems to remove the lag is software rendering.

@Fish1 commented on GitHub (Jun 7, 2023): No luck with reinstalling my drivers from AMD. If I hold down a key for a second, the inputs start to lag. The only option that seems to remove the lag is software rendering.
claunia commented 2026-01-31 00:00:33 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 7, 2023):

Do you perhaps use a FreeSync monitor? If so, could you try disabling dynamic refresh rate? Otherwise, the issue you're describing is definitely very very weird. Software rendering should definitely not be the only solution in this situation, because that is extremely taxing on the CPU. Unfortunately, I can't think of any way to debug this, apart from me debugging it on your exact device. 😟
You could check your debug logs with DebugView, but I suspect there won't be any. If you know your way around debug tools, or just something like Process Explorer or System Informer, and notice anything weird with, let's say unusual CPU usage on any of the threads, please let me know!

@lhecker commented on GitHub (Jun 7, 2023): Do you perhaps use a FreeSync monitor? If so, could you try disabling dynamic refresh rate? Otherwise, the issue you're describing is definitely very very weird. Software rendering should definitely not be the only solution in this situation, because that is extremely taxing on the CPU. Unfortunately, I can't think of any way to debug this, apart from me debugging it on your exact device. 😟 You could check your debug logs with [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview), but I suspect there won't be any. If you know your way around debug tools, or just something like Process Explorer or System Informer, and notice anything weird with, let's say unusual CPU usage on any of the threads, please let me know!
claunia commented 2026-01-31 00:00:34 +00:00
Author
Owner
Copy Link

@Fish1 commented on GitHub (Jun 7, 2023):

Yes, you are correct about the freesync.

I went to use the ScreenToGif tool to try and record my issue for you. But the moment I started recording, I managed to bluescreen windows (multiple times), simply by having both windows and ScreenToGif together.

But after disabling freesync (on my two monitors) everything seems to be working, and I can re-enable hardware rendering for windows terminal.

I don't really see anything happening in debug view.

Edit: tool i was using to capture my screen https://www.screentogif.com/

Edit: This might not be a windows terminal issue. My system seems to be rapidly deteriorating in stability for some reason.

@Fish1 commented on GitHub (Jun 7, 2023): Yes, you are correct about the freesync. I went to use the ScreenToGif tool to try and record my issue for you. But the moment I started recording, I managed to bluescreen windows (multiple times), simply by having both windows and ScreenToGif together. But after disabling freesync (on my two monitors) everything seems to be working, and I can re-enable hardware rendering for windows terminal. I don't really see anything happening in debug view. Edit: tool i was using to capture my screen https://www.screentogif.com/ Edit: This might not be a windows terminal issue. My system seems to be rapidly deteriorating in stability for some reason.
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 Area-Performance Help Wanted Issue-Bug Needs-Tag-Fix Priority-1 Product-Terminal
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#4911
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?