title: Weird crash log related to CALayer
body: <p>I encountered today a weird bug with an app I'm working on.
  The problem was with a catalog module. Above each page, there was a small black area, since the page didn't fill 100% the screen. Tapping on that zone would generate a crash.</p>
  
  <p>My crash log looks something like this:</p>
  
  <pre><code>Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
  Exception Codes: KERN_PROTECTION_FAILURE at 0x2fd00fec
  Crashed Thread:  0
  
  Thread 0 name:  Dispatch queue: com.apple.main-thread
  Thread 0 Crashed:
  0   QuartzCore                      0x35d812ac CA::Transaction::ensure_compat() + 0
  1   QuartzCore                      0x35da2648 CALayerMapGeometry_(CALayer*, CALayer*, void (*)(void*, CA::Mat4&lt;double&gt; const&amp;), void (*)(void*, CA::Mat4&lt;double&gt; const&amp;), void*) + 28
  2   QuartzCore                      0x35da25f8 -[CALayer convertPoint:fromLayer:] + 52
  3   UIKit                           0x32457018 -[UIView(Geometry) convertPoint:fromView:] + 68
  4   UIKit                           0x32456d40 -[UIView(Geometry) hitTest:withEvent:] + 172
  5   UIKit                           0x32456d50 -[UIView(Geometry) hitTest:withEvent:] + 188
  (...)repeat the line above^ until it reached 511
  511 UIKit                           0x32456d50 -[UIView(Geometry) hitTest:withEvent:] + 188
  </code></pre>
  
  <p>Even more, xcode ends up crashing soon after.
  The debug navigator shows me something even more weird: <a href="http://i43.tinypic.com/5txnq0.png" rel="nofollow">http://i43.tinypic.com/5txnq0.png</a> and then continued with a HUGE list of , like here: <a href="http://i41.tinypic.com/2h81ctw.png" rel="nofollow">http://i41.tinypic.com/2h81ctw.png</a></p>
  
  <p>I don't really know where to begin with...
  The catalog module is old and well tested, and something like this never happened before. 
  I know there are many variables and things that might affect the app, but if anyone could shed even a tiny bit of light on this, I would be really grateful
  As I said, I don't even know how to start approaching this matter, it doesn't look like your regular "accessing a deallocated object", "memory leak" or other problems I encountered so far</p>