All geek questions in one place

Flurry API iPhone crash simulator

My application crashes using iOS5 and iOS4.3 iPhone simulators in Xcode 4.2, the stack trace shows the BAD_ACCESS signal in the [FlurryAPI stopBackgroundTask] method.

While in iOS4.3 the simulator application only crashes when sending the application in the background, in iOS5 it always crashes. I am adding a debug navigator image showing the thread in which BAD_ACCESS occurs.

On the other hand, the application works fine using a real device.

Any ideas on how I can get more information about what is happening and why is this happening?

enter image description here

+4
source share
3 answers

I worked on this issue by adding the following: didFinishLaunchingWithOptions

#if TARGET_IPHONE_SIMULATOR [FlurryAnalytics setSessionReportsOnPauseEnabled:NO]; #endif
+7
source

Thread analytics does not work differently than the main thread. This can lead to a crash in the background thread.

+2
source

It looks like you have a zombie - you have a situation where you use the code after you have released it. The save count reaches zero, so the system cancels and reuses the memory, then you make the change through the original link. Now you have two different references to the same memory, each of which expects a different object. In your case, one of the links is within a barrage.

The reason for the differences in your device / simulator is the different memory allocation schemes used by the two architectures: it seems that the simulator uses memory very aggressively.

Enable NSZombie and run in the debugger. If you're lucky, this will give you the object and the point that it used after freeing.

Enable NSZombie: Product menu, Change Scheme ..., Run, Diagnostics tab, check Enable zombie objects.

+1
source

Source: https://habr.com/ru/post/1380022/

More articles:


All Articles