Terminal crashing on move to external monitor

[craiglowson]

Environment

Windows build number: 10.0.19013.0
Windows Terminal version (if applicable): 0.6.2951.0

On opening Windows Terminal, move the window to external monitor and app crashes after a couple of seconds. 

Laptop is on the Slow Insiders ring for Windows and this was working on the previous build (18362) but on upgrade to 19013 today, Windows Terminal is crashing if the app window is moved off the laptop display.
Laptop display was set as Main Display (so window opening there) and if external monitor set to left or right of this then app still crashes (i.e. dragging left or right off laptop display causes same behaviour). 
Setting external display as main display and spawning app window there then I don't see this issue and can move the app between monitors without problem. 

Following error is logged to Application Event Log so this may be a Windows issue (please advise?):

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: KERNELBASE.dll, version: 10.0.19013.1, time stamp: 0x6d1c8fa4
Exception code: 0xc000027b
Fault offset: 0x000000000010a7bc
Faulting process ID: 0x53e4
Faulting application start time: 0x01d599429b1508c5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 4ad4a8ec-eb6c-4cfc-a19c-4a809dab3237
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

And this Windows Error Reporting event:

Fault bucket 1583250623008362713, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.0.1910.22001
P4: 5daf7ab2
P5: StackHash12_c0a
P6: 0.0.0.0
P7: 00000000
P8: 88000fa8
P9: 0
P10: 

[zadjii-msft]

Thanks for the report! This is actually something that's being actively investigated already. I'll direct your attention to the following two threads:

/dup #3303
/dup #2277

Thanks!

[ghost]

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!