Hi,
Environment:
System Version: macOS 10.15.4 (19E266)
Kernel Version: Darwin 19.4.0
Xcode 11.4.1
Build version 11E503a
I have 6 simulators constantly running on a mac pro for a few days, and I started to notice the xcode instances started to crash (exit with -9) constantly after seeing the following system errors:
2020-05-25 00:01:26.462192-0700 0x220b500 Default 0x0 0 0 kernel: (AppleFSCompressionTypeZlib) /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-119.100.1/Common/ChunkCompression.cpp:666: /Applications/Xcode11.4.1.app/Contents/Frameworks/libclang.dylib: lzvn decode failed
2020-05-25 00:01:26.462272-0700 0x220b500 Default 0x0 0 0 kernel: decmpfs.c:1455:decmpfs_pagein_compressed: /Applications/Xcode11.4.1.app/Contents/Frameworks/libclang.dylib: err 22
2020-05-25 00:01:26.462318-0700 0x220b500 Default 0x0 0 0 kernel: (apfs) apfs_pagein:9266: faking zero data for ino 12995419730 (offset 0 xsize 1048576)
2020-05-25 00:01:26.462272-0700 0x220b500 Default 0x0 0 0 kernel: decmpfs.c:1455:decmpfs_pagein_compressed: /Applications/Xcode11.4.1.app/Contents/Frameworks/libclang.dylib: err 22
2020-05-25 00:01:26.462318-0700 0x220b500 Default 0x0 0 0 kernel: (apfs) apfs_pagein:9266: faking zero data for ino 12995419730 (offset 0 xsize 1048576)
2020-05-25 00:01:26.486945-0700 0x220b500 Default 0x0 0 0 kernel: (AppleFSCompressionTypeZlib) /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-119.100.1/Common/ChunkCompression.cpp:666: /Applications/Xcode11.4.1.app/Contents/Frameworks/libclang.dylib: lzvn decode failed
2020-05-25 00:01:26.487014-0700 0x220b500 Default 0x0 0 0 kernel: decmpfs.c:1455:decmpfs_pagein_compressed: /Applications/Xcode11.4.1.app/Contents/Frameworks/libclang.dylib: err 22
2020-05-25 00:01:26.487059-0700 0x220b500 Default 0x0 0 0 kernel: (apfs) apfs_pagein:9266: faking zero data for ino 12995419730 (offset 0 xsize 1048576)
Somehow this triggered the xcode into a bad state and crash loop. Rebooting the host solved the issue, but I'm curious if this is a known bug or if there's a good turnaround other than rebooting the host.
Thanks.
