This method should not be called on the main thread as it may lead to UI unresponsiveness

Hi guys / gals. Been having the MOST annoying crashes for ever, with multiple versions of WoW + macOS.

Looking at crash reports + logs, Apple actually warns that using this specific call will cause the exact lockups + crashes I am experiencing:

ERROR:

fault 18:32:50.188674+1030. World of Warcraft delegate_identifier:Performance Diagnostics__:::__message: This method should not be called on the main thread as it may lead to UI unresponsiveness.

LOG:

panic(cpu 8 caller 0xffffff801e00589b): userspace watchdog timeout: no successful checkins from WindowServer (2 induced crashes) in 120 seconds
WindowServer has not exited since first loaded
Panicked task 0xffffff90a0540f38: 3 threads: pid 105: watchdogd
Backtrace (CPU 8), panicked thread: 0xffffff90a19160c8
Kernel Extensions in backtrace: com.apple.driver.watchdog(1.0)

Running on a Mac Pro 2019: 3.3GHz, 12 core Xeon, 2x AMD Radeon Pro Vega II 32GB + 128GB DDR 4 running *nix (macOS)

Could someone in the dev team look at this and get back on a fix ASAP??? Getting really annoyed at downtime + risk of data loss + wear and tear on spinning backup hardware having to get back in to raid 0.

Looking at some of the below posts, e.g.: Game Freeze and Automatic reboot M1 Mac mini 16gb ram

…and many others that appear to be related, this one oversight might be the cause of a World of Woe!