Windows Terminal version

1.13.10983.0

Windows build number

10.0.19044.1645

Other Software

None

Steps to reproduce

• Use Terminal inside a typical VM
• Switch to the experimental Atlas engine
• Observe CPU load
• Try to type and experience sluggishness and even higher CPU load etc. There's a decent amount of lag and output from long commands tends to stutter into view; it's not very smooth

Expected Behavior

Was expecting that Atlas, in default/easy cases, would perform better than the old engine.

Looking ahead: IF atlas becomes the default and IF Terminal replaces all old cmd windows, then using this inside VMs is going to be a non-starter.

Actual Behavior

Extreme CPU usage and general sluggishness. Witness the firepower of this fully operational battle... I mean barely affordable Azure VM displaying nothing but the flashing cursor inside a blank Terminal window: