iOS 16 crash

It’s hard to see what’s going on here with just a snippet of backtrace. Please post a full crash report, using the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

same problem .same crash stack.

Same problem, same crash stack. Please help

Date/Time:           2022-09-21 08:45:28.6264 +0800
Launch Time:         2022-09-21 02:29:09.6542 +0800
OS Version:          iPhone OS 16.0 (20A362)
Release Type:        User
Baseband Version:    5.00.01
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread:  0


Kernel Triage:
VM - pmap_enter retried due to resource shortage
VM - pmap_enter retried due to resource shortage
VM - pmap_enter retried due to resource shortage
VM - pmap_enter retried due to resource shortage
VM - pmap_enter retried due to resource shortage


Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib        	0x00000001d95f5bc4 __abort_with_payload + 8
1   libsystem_kernel.dylib        	0x00000001d9617c14 abort_with_payload_wrapper_internal + 104 (terminate_with_reason.c:102)
2   libsystem_kernel.dylib        	0x00000001d9617bac abort_with_reason + 32 (terminate_with_reason.c:116)
3   libobjc.A.dylib               	0x00000001962ef85c _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) + 116 (objc-errors.mm:199)
4   libobjc.A.dylib               	0x00000001962ef7e8 _objc_fatal(char const*, ...) + 32 (objc-errors.mm:215)
5   libobjc.A.dylib               	0x00000001962c2b50 weak_register_no_lock + 392 (objc-weak.mm:421)
6   libobjc.A.dylib               	0x00000001962c7808 objc_storeWeak + 448 (NSObject.mm:365)
7   UIKitCore                     	0x000000019f1a9e3c _UIResponderForwarderWantsForwardingFromResponder + 736 (UITouch.m:185)
8   UIKitCore                     	0x000000019f0bf470 __forwardTouchMethod_block_invoke + 44 (UIResponder.m:2141)
9   CoreFoundation                	0x000000019cf067dc __NSSET_IS_CALLING_OUT_TO_A_BLOCK__ + 24 (NSSetHelpers.m:10)
10  CoreFoundation                	0x000000019cf875a4 -[__NSSetM enumerateObjectsWithOptions:usingBlock:] + 200 (NSSetM_Common.h:157)
11  UIKitCore                     	0x000000019f28ce4c forwardTouchMethod + 236 (UIResponder.m:2140)
12  Flower                       	0x00000001027a7404 touchesBegan + 80 (UIView+Event.m:56)
13  UIKitCore                     	0x000000019f1870c4 -[UIWindow _sendTouchesForEvent:] + 356 (UIWindow.m:3159)
14  UIKitCore                     	0x000000019f186684 -[UIWindow sendEvent:] + 3284 (UIWindow.m:3480)
15  UIKitCore                     	0x000000019f185944 -[UIApplication sendEvent:] + 672 (UIApplication.m:12503)
16  UIKitCore                     	0x000000019f185000 __dispatchPreprocessedEventFromEventQueue + 7088 (UIEventDispatcher.m:2371)
17  UIKitCore                     	0x000000019f1ccd64 __processEventQueue + 5632 (UIEventDispatcher.m:2680)
18  UIKitCore                     	0x000000019f4d54dc __eventFetcherSourceCallback + 224 (UIEventDispatcher.m:2752)
19  CoreFoundation                	0x000000019cfd222c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1974)
20  CoreFoundation                	0x000000019cfde614 __CFRunLoopDoSource0 + 176 (CFRunLoop.c:2018)
21  CoreFoundation                	0x000000019cf6257c __CFRunLoopDoSources0 + 340 (CFRunLoop.c:2063)
22  CoreFoundation                	0x000000019cf77eb8 __CFRunLoopRun + 836 (CFRunLoop.c:2970)
23  CoreFoundation                	0x000000019cf7d1e4 CFRunLoopRunSpecific + 612 (CFRunLoop.c:3390)
24  GraphicsServices              	0x00000001d5d9d368 GSEventRunModal + 164 (GSEvent.c:2196)
25  UIKitCore                     	0x000000019f42cd88 -[UIApplication _run] + 888 (UIApplication.m:3726)
26  UIKitCore                     	0x000000019f42c9ec UIApplicationMain + 340 (UIApplication.m:5316)
27  Flower                       	0x0000000104214800 main + 152 (main.m:18)
28  dyld                          	0x00000001bb2a1948 start + 2504 (dyldMain.cpp:1168)

Just to be clear, for me to offer any input on this I need to see a full crash report, not just a snippet. Please post a full report, using the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Please find

Thanks for the full crash report.

Consider the backtrace of your crashing thread:

Thread 0 Crashed:
0  libsystem_kernel.dylib … __abort_with_payload + 8
1  libsystem_kernel.dylib … abort_with_payload_wrapper_internal + 104 …
2  libsystem_kernel.dylib … abort_with_reason + 32 …
3  libobjc.A.dylib        … _objc_fatalv(unsigned long long, unsigned long…
4  libobjc.A.dylib        … _objc_fatal(char const*, ...) + 32 …
5  libobjc.A.dylib        … weak_register_no_lock + 392 (objc-weak.mm:421)
6  libobjc.A.dylib        … objc_storeWeak + 448 …
7  UIKitCore              … _UIResponderForwarderWantsForwardingFromRespon…
8  UIKitCore              … __forwardTouchMethod_block_invoke + 44 …
9  CoreFoundation         … __NSSET_IS_CALLING_OUT_TO_A_BLOCK__ + 24 …
10 CoreFoundation         … -[__NSSetM enumerateObjectsWithOptions:usingBl…
11 UIKitCore              … forwardTouchMethod + 236 …
12 KFlower                … touchesBegan + 80 …
13 UIKitCore              … -[UIWindow _sendTouchesForEvent:] + 356 …
14 UIKitCore              … -[UIWindow sendEvent:] + 3284 … 
15 UIKitCore              … -[UIApplication sendEvent:] + 672 …

Frames 4 through 0 indicate that the Objective-C runtime deliberately crashed your process. Frame 5 is associated with this line in the runtime [1], which has this message:

Cannot form weak reference to instance (%p) of class %s. It is
possible that this object was over-released, or is in the process of
deallocation.

This strongly suggests a memory management problem. And that raises the perennial question: Is the problem with iOS? Or with your code?

My usual answer to such question is to thorough test your app with the standard memory debugging tools enabled. They might make the problem more reproducible, and you can debug from there.

However, if I had to guess I’d say that this was an OS problem. If the above doesn’t yield anything interesting, I recommend that you file a bug about this with whatever information you have available.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] This line is to the macOS 12.5 code, which is slightly different from the iOS 16 code, which is why the line number is off by one.

We are getting the same issue mostly on iOS16. The issue happened when keyboard was opened. We don't receive close event from keyboard, crash happened before close.

Please forgive me for my poor English ~~~

我有个必现路径（I can reproduce the problem）：

1. 系统必须是iOS16.x | iOS15.6.x 等新系统（os version is iOS16.x or 15.6.x)
2. 在任何一个输入框唤起三方键盘（Evoking the Third party keyboard in any TextView）
3. 隐藏键盘（Stow the keyboard)
4. 双击或快速多次点击输入框（double click(or click more times) the Textfield)

Then you got a Crash !!!

We are getting the same issue mostly on iOS16. The issue happened when keyboard was opened. We don't receive close event from keyboard, crash happened before close.

same crash with remote keyboard.

We are getting the same crash with third party keyboard in iOS 16 only.

The crash happened when multiple click on UITextView.

same crash

I can reproduce the problem

Has anyone filed a bug about this? If so, please post the bug number.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

The same question：[https://developer.apple.com/forums/thread/711820)%C2%A0The cause of the crash was: "Cannot form weak reference to instance of class _UIRemoteInputViewController. It is possible that this object was over-released, or is in the process of deallocation." 

I got same problem.

The pre-requisites to reproduce the crash are to have:

• an iOS version 16.x.x ~ 16.2
• Using a third-party keyboard and using multiple fingers to quickly click on the UITextField and other views at the same time can cause crashes.