Crash in com.apple.CFNetwork.CacheDB-write

The crash happens when the app is InTune protected.

Ah, that probably explains something very strange about the crash report you posted. At the end of the binary images section I see this:

Binary Images:
    …
    0x0 - 0xffffffffffffffff ??? unknown-arch  <00000000000000000000000000000000> ???

which suggests that the process state has been mushed in some non-obvious way.

Are you able to test without that feature? And in that case do you ever see this problem?

I am also filing a crash report here.

To be clear, DevForums is not somewhere for filing bugs. See tip 1 in Quinn’s Top Ten DevForums Tips.

Oh, and while you’re there, check out tip 5 for info on how to include chunks of preformatted text so that the result is readable.

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

Thanks Quinn. We do not see the crash if InTune features is turned off. I found a work around by forcing NSURLCache to use in memory cache only and I dont see this crash anymore. But now we are seeing a different crash, also under InTune:

Incident Identifier: 6400C4FE-FD18-4370-9E49-6955307AE2B4
Hardware Model:      iPhone12,5
Process:             Global Relay [24836]
Path:                /private/var/containers/Bundle/Application/70DEBAF8-99D4-4ADB-8ABB-E7A386D708A6/Global Relay.app/Global Relay
Identifier:          com.globalrelay.gr-app-im
Version:             2.9.0 (33231)
AppStoreTools:       14C17
AppVariant:          1:iPhone12,5:16
Beta:                YES
Code Type:           ARM-64 (Native)
Role:                Non UI
Parent Process:      launchd [1]
Coalition:           com.globalrelay.gr-app-im [2457]

Date/Time:           2023-02-23 15:40:48.0996 -0800
Launch Time:         2023-02-23 15:31:20.2067 -0800
OS Version:          iPhone OS 16.3 (20D47)
Release Type:        User
Baseband Version:    4.00.00
Report Version:      104

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Subtype: KERN_MEMORY_ERROR at 0x0000000102fb002c
Exception Codes: 0x000000000000000a, 0x0000000102fb002c
VM Region Info: 0x102fb002c is in 0x102fb0000-0x103044000;  bytes after start: 44  bytes before end: 606163
      REGION TYPE                 START - END      [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      MALLOC guard page        102fac000-102fb0000 [   16K] ---/rwx SM=ZER  
--->  mapped file              102fb0000-103044000 [  592K] r--/rw- SM=COW  ...t_id=f5eefeef
      __TEXT                   103044000-10304c000 [   32K] r-x/rwx SM=COW  ...eMAMSwiftStub
Termination Reason: SIGNAL 10 Bus error: 10
Terminating Process: exc handler [24836]

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   dyld                          	0x00000001abad4518 dyld4::PrebuiltLoaderSet::objcClassOpt() const + 0 (PrebuiltLoader.cpp:1617)
1   dyld                          	0x00000001abad448c dyld4::APIs::_dyld_for_each_objc_class(char const*, void (void*, bool, bool*) block_pointer) + 48 (DyldAPIs.cpp:2190)
2   libobjc.A.dylib               	0x0000000186301ac8 getClass_impl(char const*) + 176 (objc-opt.mm:404)
3   libobjc.A.dylib               	0x00000001862fee5c getClassExceptSomeSwift(char const*) + 24 (objc-runtime-new.mm:1790)
4   libobjc.A.dylib               	0x00000001862fd77c look_up_class + 92 (objc-runtime-new.mm:7838)
5   Foundation                    	0x000000018750b970 NSClassFromString + 156 (NSObjCRuntime.m:0)
6   FrontBoardServices            	0x00000001a2ef1e94 +[FBSSceneClientSettingsDiff diffFromSettings:toSettings:] + 96 (FBSSceneClientSettingsDiff.m:27)
7   FrontBoardServices            	0x00000001a2ef19ac -[FBSScene _calloutQueue_comsumeLock_updateClientSettings:withTransitionContext:] + 128 (FBSScene.m:294)
8   FrontBoardServices            	0x00000001a2ef18ac -[FBSScene updateClientSettings:withTransitionContext:] + 128 (FBSScene.m:117)
9   FrontBoardServices            	0x00000001a2ef17fc -[FBSScene updateClientSettingsWithTransitionBlock:] + 116 (FBSScene.m:132)
10  FrontBoardServices            	0x00000001a2ef175c -[FBSScene updateClientSettingsWithBlock:] + 124 (FBSScene.m:122)
11  UIKitCore                     	0x000000018f423230 -[FBSScene(UIApp) updateUIClientSettingsWithBlock:] + 168 (FBSScene+UIApp.m:48)
12  UIKitCore                     	0x000000018f7219c4 -[UIApplication _setIdleTimerDisabled:forReason:] + 188 (UIApplication.m:1900)
13  Foundation                    	0x0000000187565308 __NSFireTimer + 96 (NSTimer.m:280)
14  CoreFoundation                	0x000000018d23d32c __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32 (CFRunLoop.c:1797)
15  CoreFoundation                	0x000000018d1f99a8 __CFRunLoopDoTimer + 940 (CFRunLoop.c:2402)
16  CoreFoundation                	0x000000018d19d548 __CFRunLoopDoTimers + 288 (CFRunLoop.c:2560)
17  CoreFoundation                	0x000000018d1eafa0 __CFRunLoopRun + 1896 (CFRunLoop.c:3120)
18  CoreFoundation                	0x000000018d1efeb0 CFRunLoopRunSpecific + 612 (CFRunLoop.c:3418)
19  GraphicsServices              	0x00000001c73e5368 GSEventRunModal + 164 (GSEvent.c:2196)
20  UIKitCore                     	0x000000018f6e5668 -[UIApplication _run] + 888 (UIApplication.m:3758)
21  UIKitCore                     	0x000000018f6e52cc UIApplicationMain + 340 (UIApplication.m:5348)
22                                	0x0000000103720b78 0x1034ac000 + 2575224
23                                	0x00000001023feac0 main + 640 (main.m:40)
24  dyld                          	0x00000001abae8960 start + 2528 (dyldMain.cpp:1170)

Sorry, post the reply too soon. The crash happened when the app is in the background for over an hour. We do have the app scheduled for background fetch every half an hour, without InTune it works well. I am not sure if this crash is related to the refresh, but it does have the setIdleTimerDisable call in the call stack. Was this part of the scheduled refresh triggered by OS? Thanks a lot for your help!

I think you need to talk to the InTune folks about this. You’re seeing mysterious crashes in unrelated parts of the OS when enabling there stuff. That’s not good.

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