Same issue here on Windows 11 w/ EN latest client build 3911.
Interestingly enough, this was a fresh install onto a brand new PC. Definitely think there's a bug lurking in 10.52.8 with local/cloud db management leading to corruption. Worst part is the corruption is lurking silently and issue manifests as dramatically elevated cpu utilization.
I am coming from legacy app version 6.x and this is not a good first impression.