Home/ Questions/Q 7428255
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T08:42:59+00:00

I am getting an intermittent crash when my application runs on an iPhone. All

  • 0

I am getting an intermittent crash when my application runs on an iPhone. All the crashes are identical and involve MKMapView Overlays (MKCircleViews) in some way.

From a typical iPhone 4s crash report:

Report Header:

Hardware Model:      iPhone4,1
Process:         EL-GPS-01 [1021]
Path: /var/mobile/Applications/61288E15-74B5-45B9-99A9-E0B58C767816/EL-GPS-01.app/EL-GPS-01
Identifier:      EL-GPS-01
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2011-11-22 15:59:41.065 +0000
OS Version:      iPhone OS 5.0.1 (9A405)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000
Crashed Thread:  6

And the crashed thread:

Thread 6 name: Dispatch queue: com.apple.root.default-priority
Thread 6 Crashed:
0 ??? 0000000000 0 + 0
1 CoreGraphics 0x319a87c2 0x31967000 + 268226
2 CoreGraphics 0x3199a9e6 0x31967000 + 211430
3 MapKit 0x37ec3564 0x37e6f000 + 345444
4 MapKit 0x37ec3652 0x37e6f000 + 345682
5 MapKit 0x37ecc0a4 0x37e6f000 + 381092
6 QuartzCore 0x3341be18 0x33410000 + 48664
7 QuartzCore 0x334d77e0 0x33410000 + 817120
8 QuartzCore 0x3346af24 0x33410000 + 372516
9 libdispatch.dylib 0x3797e892 0x3797b000 + 14482
10 libsystem_c.dylib 0x360e31ca 0x360d9000 + 41418
11 libsystem_c.dylib 0x360e30a0 0x360d9000 + 41120

When the application crashes whilst my iPhone is connected to my laptop I get the following in my output panel:

warning: check_safe_call: could not restore current frame
warning: Unable to restore previously selected frame.

The debugger gives me nothing at all, and the Issue navigator shows a crashed thread with nothing on the stack.

There is a very simple project highlighting the problem here:

https://github.com/1ndivisible/MKOverlayBug

git@github.com:1ndivisible/MKOverlayBug.git

I’m not sure how to approach this. Is there any information here that I can use? It seems the crash is originating deep in the framework.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Its a known bug. Apple have acknowledged it. There is currently no fix. All you can do is compound your graphics into fewer annotations. I have found <=3 annotations is safe.

    • 0