wsl --export excessive screen updates

[perlinside]

Windows Version

Microsoft Windows [Version 10.0.26100.7840]

WSL Version

2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Doesn't matter

Other Software

Microsoft terminal

Repro Steps

wsl --export .tar.xz --format tar.xz from a microsoft terminal session.

Example: wsl --export Ubuntu Ubuntu.tar.xz --format tar.xz
You should see some flickering of the end of the status line.
Also see an increase on GPU usage.

Expected Behavior

The progress indicator
Export in progress, this may take a few minutes. (#### MB)
The number should redraw when the number changes.

Actual Behavior

The number is being constantly redrawn. Many times per second. leading to unnecessary CPU/GPU overhead. If the number hasn't changed there is no reason to redraw it.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.