Resizing Terminal window is slow and laggy #8140

Closed
opened 2026-01-31 01:21:49 +00:00 by claunia · 2 comments
Owner

Originally created by @ghost on GitHub (May 14, 2020).

Steps to reproduce

Resizing the Terminal window is slow and laggy. It feels like I'm resizing the window of a uwp app, instead of a Terminal app. Terminals can't be slow and terminals can't have graphical lags.

Expected behavior

Resizing the window should be as smooth as resizing a windows console window.

Originally created by @ghost on GitHub (May 14, 2020). # Steps to reproduce Resizing the Terminal window is slow and laggy. It feels like I'm resizing the window of a uwp app, instead of a Terminal app. Terminals can't be slow and terminals can't have graphical lags. # Expected behavior Resizing the window should be as smooth as resizing a windows console window.
Author
Owner

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

@phgmacedo Cloud you try disabling a setting for me, to see if that helps here? Could you add "snapToGridOnResize": false to your settings.json file? That setting forces the terminal to try and snap to the nearest character size - if you disable it, the Terminal will resize more smoothly.

I'm not saying that resizing isn't slow, it's one of the worst functions in the codebase. Heck, optimizing it is what #5800 is all about. But the above setting might make it feel smoother, at least for now.

@zadjii-msft commented on GitHub (May 14, 2020): @phgmacedo Cloud you try disabling a setting for me, to see if that helps here? Could you add `"snapToGridOnResize": false` to your `settings.json` file? That setting forces the terminal to try and snap to the nearest character size - if you disable it, the Terminal will resize more smoothly. I'm not saying that resizing _isn't_ slow, it's one of the worst functions in the codebase. Heck, optimizing it is what #5800 is all about. But the above setting might make it _feel_ smoother, at least for now.
Author
Owner

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

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (May 18, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8140