I tried to post a device crash report which has more information but the forum software tells me it has an invalid character, but not which character or were it is located?
Post
Replies
Boosts
Views
Activity
Partial crash report see if this is allowed.Incident Identifier: BC2877C2-F7E8-4F0C-B349-F775ABBF5CD1CrashReporter Key: 67c13e1b499de3655d9d0b1ba12296189838d52aHardware Model: iPhone10,6Process: BBQSheriff [297]Path: /private/var/containers/Bundle/Application/D01A1271-499D-4613-BF3A-D072999D1EB6/BBQSheriff.app/BBQSheriffIdentifier: com.fairwindsoft.bbqsheriffVersion: 272 (1.3.1)Code Type: ARM-64 (Native)Role: ForegroundParent Process: launchd [1]Coalition: com.fairwindsoft.bbqsheriff [488]Date/Time: 2020-03-04 06:48:35.3642 -0600Launch Time: 2020-03-04 06:48:29.0308 -0600OS Version: iPhone OS 13.3.1 (17D50)Release Type: UserBaseband Version: 3.03.03Report Version: 104Exception Type: EXC_BAD_ACCESS (SIGABRT)Exception Subtype: KERN_INVALID_ADDRESS at 0x656565656565656dVM Region Info: 0x656565656565656d is not in any region. Bytes after previous region: 7306357447660561774 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL unused shlib __TEXT 0000000210000000-00000002178f0000 [120.9M] r--/r-- SM=COW ... this process---> UNUSED SPACE AT ENDTriggered by Thread: 0Thread 0 name: Dispatch queue: com.apple.main-threadThread 0 Crashed:0 libsystem_kernel.dylib 0x00000001c3a01ec4 __pthread_kill + 81 libsystem_pthread.dylib 0x00000001c3921724 pthread_kill$VARIANT$armv81 + 2162 libsystem_c.dylib 0x00000001c3871844 abort + 1003 ...g_rt.asan_ios_dynamic.dylib 0x000000010691c258 0x106898000 + 5412724 ...g_rt.asan_ios_dynamic.dylib 0x000000010690b5ec 0x106898000 + 4725565 ...g_rt.asan_ios_dynamic.dylib 0x00000001068f51ac 0x106898000 + 3813566 ...g_rt.asan_ios_dynamic.dylib 0x00000001068f3310 0x106898000 + 3735207 ...g_rt.asan_ios_dynamic.dylib 0x00000001068f2c8c 0x106898000 + 3718528 libsystem_platform.dylib 0x00000001c3918894 _sigtramp + 569 QuartzCore 0x00000001ca691c94 CA::Layer::retain_parent+ 1395860 (CA::Transaction*) const + 4410 QuartzCore 0x00000001ca6a0988 CALayerGetSuperlayer + 5211 UIKitCore 0x00000001c812fd3c -[UIView+ 15347004 (UIKitManual) superview] + 4812 UIKitCore 0x00000001c8062f40 -[UILayoutGuide _snipReferencingConstraints] + 42413 UIKitCore 0x00000001c8062254 -[UILayoutGuide _owningViewIsDeallocating] + 4014 UIKitCore 0x00000001c80f7cc4 -[UIView _layoutConstraintCleanup] + 21215 UIKitCore 0x00000001c80f7eb4 -[UIView dealloc] + 14816 UIKitCore 0x00000001c7e1a298 -[UITableViewCellContentView dealloc] + 7617 libobjc.A.dylib 0x00000001c394740c _object_remove_assocations + 35218 libobjc.A.dylib 0x00000001c3943d88 objc_destructInstance + 10019 libobjc.A.dylib 0x00000001c394adb0 _objc_rootDealloc + 4820 QuartzCore 0x00000001ca6877b4 -[CALayer dealloc] + 18821 QuartzCore 0x00000001ca611028 CA::release_objects+ 868392 (X::List<void const*>*) + 3222 QuartzCore 0x00000001ca611138 CA::release_root_if_unused+ 868664 (CA::Layer*, CA::Layer*, void*) + 5223 QuartzCore 0x00000001ca5976ac x_hash_table_remove_if + 8424 QuartzCore 0x00000001ca6114a0 CA::Transaction::commit+ 869536 () + 46425 QuartzCore 0x00000001ca611f68 CA::Transaction::observer_callback+ 872296 (__CFRunLoopObserver*, unsigned long, void*) + 9226 CoreFoundation 0x00000001c3b87e68 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 3227 CoreFoundation 0x00000001c3b82d54 __CFRunLoopDoObservers + 41628 CoreFoundation 0x00000001c3b83320 __CFRunLoopRun + 130829 CoreFoundation 0x00000001c3b82adc CFRunLoopRunSpecific + 46430 GraphicsServices 0x00000001cdb23328 GSEventRunModal + 10431 UIKitCore 0x00000001c7c9063c UIApplicationMain + 193632 BBQSheriff 0x0000000104723dbc main + 1621436 (BBQAppDelegate.swift:22)33 libdyld.dylib 0x00000001c3a0c360 start + 4
I also have this Assert in the log. I also have a problem with the view that I am troubleshooting. I guess we just ignore it for now?
I'd like to the known the answer to this also. I end up deleting DerivedData 5 to 10 times per day on a a large project. Often I get corrupted database error, but just rebuilding again seems to fix it.
I am having the a similar problem, any solution.