Exc_Bad_Access at Lauch for Eaglcontext Renderbufferstorage: Fromdrawable: in Cocos2D App Whie Debugging

EXC_BAD_ACCESS at lauch for EAGLContext renderbufferStorage: fromDrawable: in Cocos2d app whie debugging

Looks like this is an issue on certain devices on iOS 8.3+. It works for me on almost all devices but the iPad mini 2 fails for me as well. The short of it is that there's nothing wrong with the call itself. Seems to be an Xcode bug with those devices for some reason. You can get around it (until Apple fixes it) by:

In Xcode, go to Product -> Scheme -> Edit Scheme ...
And for the Run Debug configuration (on left side) choose "Options" (on right side) and configure "GPU Frame Capture" as Disabled.

For more information, check out this thread:
https://github.com/BradLarson/GPUImage/issues/2022#issuecomment-118943746

MKMapView crash on iPod when Re-enter in view

By this solution didUpdateUserLocation method is not called and you are not able to get user location internally from didUpdateUserLocation method but until Apple not fixes it.This is the only solution i got from the link EXC_BAD_ACCESS at lauch for EAGLContext renderbufferStorage: fromDrawable: in Cocos2d app whie debugging
which i do and remove the crash.

In Xcode, go to Product -> Scheme -> Edit Scheme ... And for the Run Debug configuration (on left side) choose "Options" (on right side) and configure "GPU Frame Capture" as Disabled.

My app crashes when running on my iPhone, but not in the simulator. What are some debugging techniques I can use to reso the issue?

Turns out it was a bug with xcode rather than any code, as seen in this question: EXC_BAD_ACCESS at lauch for EAGLContext renderbufferStorage: fromDrawable: in Cocos2d app whie debugging.

Apparently EAGLcontext_renderBufferStorage can cause errors on iOS 8.3+. The solution to this is to change the scheme that you are using to disable GPU Frame Capture. Not entirely sure why this works, but it does!



Related Topics



Leave a reply



Submit