So I'm loading some images from files which I saved in the app's document directory and upon completion, I update a dictionary which holds all the images for my tableview. So far so good, everything's working just fine.
But now I've stumbled upon a really peculiar crash. Sometimes when updating the dictionary the app crashes, giving me the error message: "Heap corruption detected, free list is damaged at ...".
I've added a symbolic breakpoint at malloc_error_break and turned on the Address Sanitizer the Undefined Behaviour Sanitizer and Zombie Objects as advised in this post: iOS error : Heap corruption detected, free list is damaged and Incorrect guard value: 0
Now I'm getting the following error message, which doesn't really help me either:
2019-06-09 17:35:20.806306+0200 Wizy[9953:3221129] -[NSIndexPath count]: unrecognized selector sent to instance 0x8000000000000000
2019-06-09 17:36:28.490834+0200 Wizy[9953:3221129] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSIndexPath count]: unrecognized selector sent to instance 0x8000000000000000'
*** First throw call stack:
(0x1fc9d7ea0 0x1fbba9a40 0x1fc8f0d04 0x1fc9dd7b8 0x1fc9df45c 0x10952fbdc 0x10952fb5c 0x104868004 0x10461a178 0x104b59fd8 0x1045e4bd0 0x1067817c8 0x10a093824 0x10a094dc8 0x10a0a6330 0x10a0a6bc8 0x1fc5f417c 0x1fc5f6cec)
libc++abi.dylib: terminating with uncaught exception of type NSException
I have no clue as to what could've caused that crash, hopefully someone can help me out here!
Related
I've been trying to figure out this bug for a long while, and i can't figure out where the error is (I have a debug point literally everywhere in my code), and I was wondering if I could use the error to find out where it is (ie figure out what instance 0x100b15ad0 is)
Fun Error Below:
2016-10-21 23:09:56.870436 AppName[1992:639323] -[AppName.ScannerView unhighlight]: unrecognized selector sent to instance 0x100b15ad0
2016-10-21 23:09:56.871918 AppName[1992:639323] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[AppName.ScannerView unhighlight]: unrecognized selector sent to instance 0x100b15ad0'
*** First throw call stack:
(0x1851001c0 0x183b3855c 0x185107278 0x185104278 0x184ffe59c 0x185be7988 0x1850ae8f4 0x1850ae608 0x1850adec4 0x1850abac0 0x184fda048 0x186a5d198 0x18afb3818 0x18afae550 0x100024994 0x183fbc5b8)
libc++abi.dylib: terminating with uncaught exception of type NSException
I'm testing the Sphero-AR-SDK found on GitHub (https://github.com/orbotix/Sphero-AR-SDK)
When testing, I seem to have random crashes on connect.
The issue I'm trying to debug is an index out of range error.
*"*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 0 beyond bounds for empty array'
*** First throw call stack:
(0x325102a3 0x3a22d97f 0x3245bb75 0x8cb42b 0x32e270f5 0x324e5683 0x324e4ee9 0x324e3cb7 0x32456ebd 0x32456d49 0x3602d2eb 0x3436c301 0x7f10 0x3188)
libc++abi.dylib: terminate called throwing an exception"*
This happens a fair amount when booting the application but not all the time (sometimes it will get through and play the game).
I was wondering if anyone else was having issues with these random crashes or have I not set it up correctly?
I've had a look at the "Other Linker Flags" in XCode too and it has -all_load.
Also, I've safely checked the only place where I could find an array object access in the .mm files (RKUNBridge.mm) has this line:
[RKDeviceSensorsData *data = [sensors_data.dataFrames objectAtIndex:0];
And I safely checked this array exists and is greater than one to double check it's not this line.
Any ideas or suggestions would be much appreciated.
Thanks for reading.
Ok so yesterday I had some trouble with this error, turned out I just needed to be patient and read through more of the book. This time I have got to the end of the project and I am getting this error at a different point.
I have isolated the line of code causing the issue but I'm not sure what the issue is!
htmlString=[htmlString stringByAppendingString: appDelegate.savedNumber];
Debug console is saying:
2012-08-09 13:06:47.235 tester[1357:c07] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[__NSCFConstantString stringByAppendingString:]: nil argument'
*** First throw call stack:
(0x14b3022 0xeb3cd6 0x145ba48 0x145b9b9 0x941b92 0x29bd 0xdda1e 0x3c401 0x3c670 0x3c836 0x4372a 0x24c2 0x14386 0x15274 0x24183 0x24c38 0x18634 0x139def5 0x1487195 0x13ebff2 0x13ea8da 0x13e9d84 0x13e9c9b 0x14c65 0x16626 0x20e2 0x2055)
terminate called throwing an exception
Anyone have any ideas? :)
It is because appDelegate.savedNumber is nil (does not set) . And why it is nil this is another question.
Looks like exactly what's written, you're passing nil argument to the method. Check if your savedNumber is a valid string object.
Ive developed an app for iPhone. Ive successfully tested it in the iPhone Simulator, but as soon as I run it on my test iDevice, it throws an error:
Error reading plist: stream had too few bytes, format: 1064028076
How could it have an error if it works correctly on the sim?
2012-03-23 10:40:16.791 Ask Alarm[5697:707] Error reading plist: stream had too few bytes,
format: 1064028076
2012-03-23 10:40:16.807 Ask Alarm[5697:707] 2012-03-23 17:40:16 +0000
2012-03-23 10:40:16.814 Ask Alarm[5697:707] *** Terminating app due to uncaught exception
'NSInvalidArgumentException', reason: '*** -[__NSCFString stringByAppendingString:]: nil
argument'
*** First throw call stack:
(0x32b818bf 0x358491e5 0x32b817b9 0x32b817db 0x3216b121 0x697dd 0x36ba57ff 0x36c063b9 0x36c06357 0x36c05c91 0x36c08661 0x36c081a7 0x36bae6b5 0x36c0961b 0x36c4f691 0x36c4e14f 0x3028e93 0x36ca8d97 0x32adb435 0x36b879eb 0x36b879a7 0x36b87985 0x36b876f5 0x36b8802d 0x36b8650f 0x36b85f01 0x36b6c4ed 0x36b6bd2d 0x337f0df3 0x32b55553 0x32b554f5 0x32b54343 0x32ad74dd 0x32ad73a5 0x337effcd 0x36b9a743 0x670ab 0x669a8)
terminate called throwing an exception(lldb)
It's either a mis-formatted plist file or something is bogus in your stringByAppendingString call.
Check both for anything obvious and if you don't see it, modify your question to add a bit of the code (both the plist and the code that includes the stringByAppendingString line)
need help desperately ahead of a demo in a few hours... App was working on my test device fine last night. Added some data (as I always do) this morning and now I get this error during a save operation:
Serious application error. Exception was caught during Core Data change processing:
*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value
(key: _ContentChange_OldIndexPathKey) with userInfo (null)
*** Terminating app due to uncaught exception 'NSInvalidArgumentException',
reason: '*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value
(key: _ContentChange_OldIndexPathKey)'
The funny thing is that if I download my sqlite file to my Mac and feed it into the simulator, everything works just fine. The crash only occurs on the test device.
Any ideas?
I too was encountering this error. Nullifying the NSFetchedResultsController delegate does stop it from crashing, but is not a fix. The problem seems to be specifying a sort key in the NSFetchRequest which is null for some objects. Some sort call made in NSFetchedResultsController expects none null values.
This is an old post but I will give my comment anyway :)
I have experienced similar problem and deleting the cache for the NSFethedReultController solved the problem.
[NSFetchedResultsController deleteCacheWithName:<cacheName>];