Sign in to follow this  

OpenGL opengl es analysis tool crashes when i run my app

Recommended Posts

I am developing a game on Xcode 4 with opengl es on ipad. I am getting a low fps ,i tried to run it with performance tools --- "opengl es analyzer" that comes with xcode 4 but as soon as i run it i get exception

[b]*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSCFArray objectForIntKey:]: unrecognized selector sent to instance 0x11812cdd0'[/b]

[b]*** Call stack at first throw:[/b]


[b] [/b][b]0 CoreFoundation 0x00007fff867117b4 __exceptionPreprocess + 180[/b]

[b] [/b][b]1 libobjc.A.dylib 0x00007fff890670f3 objc_exception_throw + 45[/b]

[b] [/b][b]2 CoreFoundation 0x00007fff8676b110 +[NSObject(NSObject) doesNotRecognizeSelector:] + 0[/b]

[b] [/b][b]3 CoreFoundation 0x00007fff866e391f ___forwarding___ + 751[/b]

[b] [/b][b]4 CoreFoundation 0x00007fff866dfa68 _CF_forwarding_prep_0 + 232[/b]

[b] [/b][b]5 GPUToolsAnalysis 0x0000000118034ac6 -[DYStateMirror setStateEntry:forKey:dictNum:subDictNum:thirdDictNum:preexistingRetCode:] + 73[/b]

[b] [/b][b]6 GPUToolsAnalysis 0x000000011803759c -[DYStateMirror applyFunction:functionIndex:] + 8422[/b]

[b] [/b][b]7 GPUToolsAnalysis 0x0000000118017961 -[DYAnalyzerHeuristicPool processFunction:captureBlockMode:functionIndex:] + 606[/b]

[b] [/b][b]8 GPUToolsAnalysis 0x000000011801440e -[DYAnalyzerEngine processFunctionStream:blockMode:findingsHandler:] + 269[/b]

[b] [/b][b]9 OpenGLESAnalyzerInstrument 0x0000000113e115ef 0x0 + 4628485615[/b]

[b] [/b][b]10 libSystem.B.dylib 0x00007fff85165284 _dispatch_call_block_and_release + 15[/b]

[b] [/b][b]11 libSystem.B.dylib 0x00007fff85143df2 _dispatch_queue_drain + 251[/b]

[b] [/b][b]12 libSystem.B.dylib 0x00007fff85143c54 _dispatch_queue_invoke + 57[/b]

[b] [/b][b]13 libSystem.B.dylib 0x00007fff851437fe _dispatch_worker_thread2 + 252[/b]

[b] [/b][b]14 libSystem.B.dylib 0x00007fff85143128 _pthread_wqthread + 353[/b]

[b] [/b][b]15 libSystem.B.dylib 0x00007fff85142fc5 start_wqthread + 13[/b]


And the crashed thread is:

[b]Thread 10 Crashed: Dispatch queue:<OGLARun: 0x116ae4c90>[/b]

[b]0 libSystem.B.dylib [/b][b] [/b][b]0x00007fff8519be4e __semwait_signal_nocancel + 10[/b]

[b]1 libSystem.B.dylib [/b][b] [/b][b]0x00007fff8519bd50 nanosleep$NOCANCEL + 129[/b]

[b]2 libSystem.B.dylib [/b][b] [/b][b]0x00007fff851f86ae usleep$NOCANCEL + 57[/b]

[b]3 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85217c81 __abort + 113[/b]

[b]4 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85217ce5 abort_report_np + 0[/b]

[b]5 libstdc++.6.dylib [/b][b] [/b][b]0x00007fff860d75d2 __tcf_0 + 0[/b]

[b]6 libobjc.A.dylib [/b][b] [/b][b]0x00007fff8906ad29 _objc_terminate + 100[/b]

[b]7 libstdc++.6.dylib [/b][b] [/b][b]0x00007fff860d5ae1 __cxxabiv1::__terminate(void (*)()) + 11[/b]

[b]8 libstdc++.6.dylib [/b][b] [/b][b]0x00007fff860d5b16 __cxxabiv1::__unexpected(void (*)()) + 0[/b]

[b]9 libstdc++.6.dylib [/b][b] [/b][b]0x00007fff860d5bfc __gxx_exception_cleanup(_Unwind_Reason_Code, _Unwind_Exception*) + 0[/b]

[b]10 libobjc.A.dylib [/b][b] [/b][b]0x00007fff89067192 object_getIvar + 0[/b]

[b]11 [/b][b] [/b][b]0x00007fff8676b110 +[NSObject(NSObject) doesNotRecognizeSelector:] + 0[/b]

[b]12 [/b][b] [/b][b]0x00007fff866e391f ___forwarding___ + 751[/b]

[b]13 [/b][b] [/b][b]0x00007fff866dfa68 _CF_forwarding_prep_0 + 232[/b]

[b]14 [/b][b] [/b][b]0x0000000118034ac6 -[DYStateMirror setStateEntry:forKey:dictNum:subDictNum:thirdDictNum:preexistingRetCode:] + 73[/b]

[b]15 [/b][b] [/b][b]0x000000011803759c -[DYStateMirror applyFunction:functionIndex:] + 8422[/b]

[b]16 [/b][b] [/b][b]0x0000000118017961 -[DYAnalyzerHeuristicPool processFunction:captureBlockMode:functionIndex:] + 606[/b]

[b]17 [/b][b] [/b][b]0x000000011801440e -[DYAnalyzerEngine processFunctionStream:blockMode:findingsHandler:] + 269[/b]

[b]18 ....OpenGLESAnalyzerInstrument[/b][b] [/b][b]0x0000000113e115ef 0x113e05000 + 50671[/b]

[b]19 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85165284 _dispatch_call_block_and_release + 15[/b]

[b]20 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85143df2 _dispatch_queue_drain + 251[/b]

[b]21 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85143c54 _dispatch_queue_invoke + 57[/b]

[b]22 libSystem.B.dylib [/b][b] [/b][b]0x00007fff851437fe _dispatch_worker_thread2 + 252[/b]

[b]23 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85143128 _pthread_wqthread + 353[/b]

[b]24 libSystem.B.dylib [/b][b] [/b][b]0x00007fff85142fc5 start_wqthread + 13[/b]


could anyone point me in the right direction how do i get around this problem


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now