User Profile

After updating to Xcode 15.3 , Xcode will crash soon after open my project , and my project works fine for years and after I reset Xcode to 15.2 . my project can work well . so I think this is a problem brought by Xcode 13 ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Xcode [26747] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497799835 App External ID: 863955376 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-03-28 15:34:04.5862 +0800 OS Version: macOS 14.1.1 (23B81) Report Version: 12 Anonymous UUID: 0B2BF703-3E8D-CF6D-2498-8380353F5495 Time Awake Since Boot: 1400 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000019b43065c Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [26747] Thread 0 Crashed: 0 libswiftCore.dylib 0x19b43065c _assertionFailure(_:_:file:line:flags:) + 268 1 IDEXCBuildSupportCore 0x178f5ea3c specialized _NativeDictionary.merge<A>(_:isUnique:uniquingKeysWith:) + 928 2 IDEXCBuildSupportCore 0x178f66320 specialized IDEXCBuildServiceBuildOperation.processEventStream(buildOperation:events:logger:context:) + 1164 3 IDEXCBuildSupportCore 0x178f6f885 closure #1 in closure #3 in IDEXCBuildServiceBuildOperation.performCoreBuild() + 1 4 IDEXCBuildSupportCore 0x178f62f5d partial apply for closure #1 in closure #3 in IDEXCBuildServiceBuildOperation.performCoreBuild() + 1 5 IDEXCBuildSupportCore 0x178f261b9 specialized thunk for @escaping @callee_guaranteed @Sendable @async () -> (@out A) + 1 6 IDEXCBuildSupportCore 0x178f26891 partial apply for specialized thunk for @escaping @callee_guaranteed @Sendable @async () -> (@out A) + 1 7 libswift_Concurrency.dylib 0x22ad89c7d completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1

I think the most important feature for iOS native-developers is the Hot-Update(Because it's so hard to force your app's users to upgrade in AppStore), And this is the reason why so many cross-platform technologies are needed . Is there any chances that Apple will issue a official Hot-Upgrade mechanism for this ? And I think it's not very hard to Apple to achieve this .

I found that ,If a Parent View was CATiledLayer based, it will deallocating its SubView's layer before the SubView object is deallocating it self (When SubView object is retained in some async opertaions, and Parent View is deallocating). This can cause some zombie memory issues. If the Parent View is CALayer based , everything is OK. I have done a zombie profiling for both layers situations. Seems the only diffrence between them is _UIViewWillBeRemovedFromSuperview will be called only for CALayer based ParentView , and without _UIViewWillBeRemovedFromSuperview called , the SubView's layer object 's reference count seem wrong and the zombie object comes out demo code can be found here: demo code - https://github.com/ximmyxiao/TestTiledLayerDealloc It seems that addSubView is not permit for CATiledLayer based View?