Pro Tools locks up moving windows

[LukeHoward]

Moving the Edit window between monitors with different scale factors (from non-retina to retina) seems to lockup 2020.5, at least in the case where the session's saved window state is on the non-retina display. It appears there is a modal dialog but it's drawn as a white rectangle (suspect it's reporting an assertion failure). Clicking in it to dismiss it leaves me with an incompletely drawn Edit window.

Looking at the logs, it does appear that it's an assertion failure related to scale factors.

340788.742584,00307,0e0f: PtApp_Assert(Release): "destScale == 1 || srcScale == 2 || inResolution == eResolution_InPoints", /Volumes/Development/protools/release/2020/r1/ProTools/DFW/Imaging/MacOS/DFW_PainterQ
uartz.mm Line 2576, Thread: Main Thread (id=kThreadTableID_MainThread)
Stacktrace:
        0x1168e2d00 : - (Pro Tools @ 0x115c60000)
        0x101f86af4 : - (CFnd @ 0x101f84000)
        0x101f86a6d : - (CFnd @ 0x101f84000)
        0x10243f030 : - (DFW @ 0x1022f7000)
        0x10241ff54 : - (DFW @ 0x1022f7000)
        0x11b8c491d : - (Pro Tools @ 0x115c60000)
        0x10241f7a5 : - (DFW @ 0x1022f7000)
        0x102308747 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x102308868 : - (DFW @ 0x1022f7000)
        0x10231465b : - (DFW @ 0x1022f7000)
        0x7fff326a01ff : - (AppKit @ 0x7fff324d4000)
...
340788.746056,00307,0f09: Alert: Assertion in "/Volumes/Development/protools/release/2020/r1/ProTools/DFW/Imaging/MacOS/DFW_PainterQuartz.mm", line 2576.

PS. Does Avid have a bug reporter interface? Seems like this group isn't always monitored, and I'm not going to purchase an ASC to report a bug.

[LukeHoward]

For context: I have two monitors, one HiDPI, one not. GPU is a W5700X, macOS 10.15.4, Pro Tools 2020.5. It would seem the source and destination scale are inverted (that which is triggering the assertion failure).

[[email protected]]

Yup, I've had the same thing all day with 2020.3. Pretty frustrating. Hopefully a fix comes out soon.