> On Sep 12, 2017, at 2:03 PM, dyowee <csharpenthusi...@gmail.com> wrote: > > I understand sir. What about the size/length of the json string? Would that > cause an issue/crash?
No. The method is not supposed to crash, period. (Unless it's given a bad pointer, or the heap has been corrupted or something, of course.) There are three possibilities: CBL is passing a bad pointer or a dealloced object or something like that. There's a bug in Apple's NSJSONSerialization implementation. Some code in your app has corrupted the heap. 1 seems unlikely because you're the only one to have reported this bug, so apparently it doesn't happen in other people's apps. Also, a bug like this tends to crash immediately in the Obj-C runtime the first time the bad object is called. 2 also seems unlikely given how many developers Apple has, and that the NSJSONSerialization code has been around for about six years. As for 3, have you used the Xcode Address Sanitizer and Static Analyzer to look for potential memory bugs? —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/2458AE8C-FE0D-49BB-8202-D163A0AB4556%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
