I have a memory leak in my iOS app, some of the leaks were due to my code written which i was able to fix. But this i was unable to know what the issue was. Any one who can help me with this.
This is the screenshot for reference:
Related
I've used Xcode's zombie debugger and managed to find this flag upon launch:
This crashed the app, and re-recording from Instruments caused the same result. Relaunching the app from the device made the app launch without a crash and subsequent launches from Instruments resulted in normal operation without flags or crashes.
Can anyone make sense of this or advise? I'm getting a number of "heap corruption" crashes in production. The reports are limited to a handful of users, but I'm afraid that number is growing.
It looks like the Parse SDK's latest release notes (1.15.1) addresses this:
-Adds polygonal queries
-Fixes memory leaks related with PFCommandCache
But my crash reports are coming from builds with this SDK version.
The Parse team has responded saying that a fix for this is coming to a new SDK release soon. :)
I used Bugly(a tool same as Crashlytics) to recored crashes in my app which had released.But sometimes there are some crashes in main.m as the report showed:
With these information I can't location problem in my code at all.I need to know which class and which method the problem occured so I can location this problem.
I wonder is there any way I can location problem more precise?And how do you deal with these crashes in your released app?
Wish you can share,thanks a lot.
Finally I find this is memory leak result.Use Xcode instrument check is a good way.
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?
IN iOS 8.2 Device, my application got crashed,So to see the crash logs i connected my device to Mac (Xcode->devices->Device logs)
.There were no crash(.Crash) files generated instead “JetsamEvent-2015-03-18-151504.ips” files were generated which were of no use.And i am also using PLCrashReporter framework to collect crashes , but it is also not helpful in finding these crash files.Do anyone know why the crash file was not generated for my app crash?
Anyone have face this issue.
Thank you.
JetsamEvent log is so called Low Memory Report.
So, it is highly possible that your App was killed by system due to memory shortage.
References
- My app crashes and closes down and there is very little information as to why
- Understanding Low Memory Reports (*a little bit outdated)
I have being seeing crashes in my iOS app, when opening LA Times (www.latimes.com). The crash happens in WebCore somewhere and I have no clue where. Profiling with both "Zombie" or "leaks" do not return anything for this "EXE_BAD_ADDRESS" error.
I also checked with a small, bare UIWebView app and I could reproduce the effects.
Right now, I see this happening only with LA times, but I am not sure if there are other sites as well.
Can someone check on and guide me in what could be the possible error/source for this crash?
EDIT: I have added a small UIWebView project demonstrating this bug at
github
EDIT 2: The app (include the demo at github) works perfectly fine on iOS 7.0, but crashes in iOS 7.1 ... seems a recent bug with iOS 7.1. I have issued a bug report to Apple and will keep updated.
Thanks in advance,
Nikhil
I happened to bump into that same issue with one of my apps in iOS>7.0 only.
It seems to be a sync issue which can be fixed by creating the webview from the main thread only.
As a fix I just wrapped my UIWebView creation in a dispatch_sync(dispatch_get_main_queue(), ^{ ... });
And it solved the problem.
Of course if your code is running on the main thread you shouldn't wrap it this way ;)