EXC_BAD_ACCESS on presentRenderbuffer

When I call presentRenderBuffer , in some situations my application crashes with EXC_BAD_ACCESS. But usually everything is in order.

The call stack is here:

 #0 0x2f53f02e in glrGetPrivateInteger () #1 0x329a192e in gliGetInteger () #2 0x002eec04 in __collect_all_context_profiling_data_block_invoke () #3 0x0015ea7c in iter_contexts () #4 0x002ee7f2 in collect_all_context_profiling_data () #5 0x00163fbc in copy_profiling_data_dictionary(ContextInfo*, unsigned int, unsigned long long) () #6 0x00160566 in handle_frame_boundary () #7 0x002f194c in EAGLContext_presentRenderbuffer(EAGLContext*, objc_selector*, unsigned int) () #8 0x00044a68 in __36-[CanvasView initializeWithContext:]_block_invoke56 

Do you have any ideas about this?

SOLVE:

A texture is created and deleted in different contexts. This caused a problem.

Now a texture is created and deleted in one context. He solved the problem.

+8
objective-c ios7 rendering
source share

No one has answered this question yet.

See related questions:

261
How to save custom objects in NSUserDefaults
98
AVAudioPlayer issues a breakpoint in debug mode
17
EXC_BAD_ACCESS for mergeChangesFromContextDidSaveNotification
one
exc_bad_access rejectModalViewControllerAnimated
one
AVAssetWriterInputPixelBufferAdaptor appendPixelBuffer: EXC_BAD_ACCESS
0
exc_bad_access even with a starship class project
0
EXC_BAD_ACCESS - random and incomprehensible
0
Objective-C error with EXC_BAD_ACCESS after reading the file
0
GLKView display method crashes in [GLKView _createFramebuffer]
0
EXC_BAD_ACCESS KERN_INVALID_ADDRESS, but memory is not deleted

All Articles