objc_release crash with no origin in my code - ios

I'm getting this strange crash with no indication from where it's going. I am not able to reproduce this on my devices. Any idea what could be wrong and where to look for the problem?
It looks it happens in autorelease pool cleaning in main loop, however I am not affecting it in my app - I am using ARC. The AppDelegate.swift line 21 is just declaration of AppDelagate class.
I am not able to reproduce this problem on any of my devices (I have about 8 of them), but this crash happens to about 10% of users of the new version, so that it is pretty frequent. I tried some build as the AppStore one.
Thanks,
Jindrich

Related

iOS crash below iOS9.3 with SIGSEGV, different Crash Log

Many crashes happened below the iOS9.3 (which means devices with iOS10 are OK)..
The crash logs seem to show that it's not a problem about API that can only be used below iOS 9.3 .
But I have no idea about the crash logs. ( I'm sorry ...for I just start to study iOS development for only 2 month )
Could you please help me analyze the crash logs ?
Really Thanks !
crash log 1
crash log 2
AXE_BAD_ACCESS - this is problem with memory. One of function tried to use variable which already released. I think you need to check use your TableView and cells for this table.
Also to find problem with memory you can try to use zombies
Used to have the similar strange crashes in my app. And only in production, when testing from TestFlight. Building on device with ios 9 caused no problems.
Maybe it sounds strange, but try to convert all images you use in app to images with included sRGB color profile. For me it helped.

Unity5.2.2+Parse1.6.2+iOS9, SignupAsync causes EXC_BAD_ACCESS on iPhone

On this situation, simply "SignupAsync" causes EXC_BAD_ACCESS on real device only.
On UnityEditor, SignupAsync can be finished without error.
On any case, Users can be created on Parse Server.
How can I avoid this?
It seems "connection.data" has no "bytes" in this case.(Existing no "bytes" variable causes exc_bad_access i think.)
Is it Parse SDK bug? Or not?
I have scheduled a release of my newest game in this week, so this problem annoy me... I need anyone help.

EXC_BAD_ACCESS(Code=EXC_ARM_DA_ALIGN) Only when running app on device from Xcode

I'm getting a really weird EXC_BAD_ACCESS(Code=EXC_ARM_DA_ALIGN) crash on my app which is written in swift but only when i run it on a 32 bit device and only if its running from Xcode (the device is still hooked to Xcode), If i start the app without Xcode it runs fine. I can't give any code since no matter what i do i get no stack trace or anything like that .Only the mention error on the AppDelegate, even though the crash is in different screens further in the app (crashes on second screen).
Any idea as to why the crash would happen only when Xcode is running the app
You are using some variable or object which is yet to be initialised. Please review your code and you will get the error. You can add exceptional break point to get the actual position of the error.
It's a memory alignment issue. Search on EXC_ARM_DA_ALIGN.
https://brewx.qualcomm.com/bws/content/gi/common/appseng/en/knowledgebase/docs/kb95.html
use memcpy
char*Code; int pc;
double f;
memcpy(Code+pc, &f, sizeof(f)); // instead of *(double*)(Code+pc)=f; that generates EXC_ARM_DA_ALIGN

WebThread crashes on over-released CA object

I have built an App in Swift but with Cordova which is Obj C. I also use crashlytics. I'm seeing a crash in about 10% of users, previously I experienced it a lot myself when using the debugger but since iOS 8.3 I don't, but that doesn't seem to have reduced the problem in the wild.
The crash is EXC_BAD_ACCESS KERN_INVALID_ADDRESS in CA::release_objects(X::List<void const*>*) + 32, called when the autorelease pool is drained. The crash is always in the WebThread.
I can't seem to reproduce locally with Zombies profiling, so it is difficult to narrow down any further, but I can't see what would be causing this in my code. I do use Core Animation but only in swift, and this was happening before I added the CA code. I use UIView animations, but again it is all in Swift with Storyboards and I can't think where anything would be going wrong. Any suggestions?

CoreFoundation Trap error "Thread1:EXC_BREAKPOINT (code=EXC_ARM_BREAKPOINT, subcode=0xdefe)"

i need your help i've got this frustrating "random" error.
The app is compose of one Mapviewcontroller and a collectionview on the second controller.
Sometimes when I return to the map from the second controller the app suddenly crash with this error on the the "trap" line.
The crash report doesn't point to any of my lines of code.
EXC_BREAKPOINT (code=EXC_ARM_BREAKPOINT, subcode=0xdefe)
I said "random error" because the same version of the same app could be build and run smooth for days, then suddenly it stuck. The only way to regain control of the app is to delete manually from the iPad and rebuild.
For your information the app uses Coredata.
Any ideas? Some method to figure out where the error come from?
Any help is appreciated, thanks!
I had this error on line like that
NSLog(#"%#: tutorial view retain count = %ld",self.class,CFGetRetainCount(CFTypeRef(tutorialView)));
where tutorialView equals nil
Restart your iOS device - that worked for me. You can also try restarting Xcode.
I was getting the crash where I had a breakpoint set, but I had breakpoints turned off. I think that there are glitches in how Xcode handles breakpoints that can cause this issue even if there aren't issues in the code itself.

Resources