Build succeeded 17/12/2021 19:19 1731.0 seconds !!

The issue is still present in XCode 13.2 Final Release. This is a show stopper! Apple Devs, please soon fix the issue. Xcode is useless since 2 months. My project does not build anymore, neither with simulator or real device. Analysing the project does not work neither. Automatically running background tasks e.g. for Canvas prevent from continued software development (without user triggered build functionality). RAM memory consumption grows up to 100 GB and more. Included Swift packages compile correctly, but compilation of own modules lasts for ever in dead loop without compilation warning. There's some long lasting background build activity, if patient, the build process may finish (before the MBP resets). This behaviour is non deterministic: I've experienced the same project may compile/run after a build folder clean without any code change. I was somehow lucky to first progress with XCode 13.2 RC (13C90), but the local workaround does not work anymore. Please help out.

Unfortunately, the issue is still present within XCode 13.2 RC in 1 of my complex iOS projects. I'll reopen the issue report to Apple.

The issue appeared with XCode 13 official release. Probably, the last XCode 13 Beta was still fine.

This doesn't seem to be related to a macOS release (issue happens also on Big Sur). Some parsing mechanism is getting in some deadlock populating the same process if unresponsive. I've filed an own bug report. Sharing the feedback report reference will not help here. At least, my report was identified as critical and I've got almost immediate processing response. I've requested a possible workaround to help out faster (than a XCode bug fix).

Does Xcode 13.1 RC help to fix the issue?

Memory Consumption Issue makes working with XCode 13 impossible. Even right after a mac reboot/login, the memory request grows up to 40 GB and more right after launch of XCode. I can't find out the root cause as Xcode 13 was working since last official release 13, but suddenly the issue appeared as of today while not modifying the XCode installation (updates are configured as manual).

Seems there's not much help to be expected, neither from developers nor Apple :-( I'm trying other channels.