Let me explain what i'm having, I'm Macbook pro early 2015 user, and i updated to macOS Catalina 5 days ago, on the first day the keyboard was working fine, but they keyboard started freezing at random times (Only the power key works, others don't work).
So later i resetted the PRAM, SMC, NVRAM and it doesn't solve anything.
So i decided to downgrade to ...
Had the same stack trace and killing nvim in activity monitor unblocked all the login processes. No idea why this worked, nvim was already orphaned so shouldn't have been running anyways.
Guessing the offending program is probably different for everyone though, so if you don't use nvim maybe just look for an out of place orphaned terminal app in activity ...
I found a fix for me.
Something told me that a disabled Spotlight might be the reason (I had similar issue long time ago and re-enabling Spotlight did the job).
If you have Spotlight disabled, then re-enable it using this in Terminal:
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
After installation you can disable it ...
Before you do anything once you launch the Install macOS Catalina app - choose the window menu, show log (Command L) then show all logs (Command 3)
After a failed install, you can look at /var/log/install.log and see where it's getting stuck or at least know the last few things it has done before it gets bogged down.
I'm installing on to a Catalina volume ...
My problem was due to iCloud.
All my projects were inside documents folder which is iCloud folder.
Because iCloud settings in my MacBook was with the optimize option, the content of files weren’t allocated locally in the hard drive but remotely in iCloud. That was the cause for unresponsiveness of Xcode when loading the project or even starting new one.
I fixed my issues by clearing up some network shares that couldn't connect. I had three network shares in my user's System Preferences>Users>Login Items. These were all on a server that I couldn't connect to at the time.
For some reason when I opened either Slack or Zoom, they'd attempt to connect to that server.
I can't think why either of those apps were ...