Skip to main content

App crashing in cocos2d app on device when nothing happening



I have a somewhat simple game that I'm making and now that I'm testing what I consider a bare bone version of the app on devices, I keep getting crashes over and over. I'm fairly new at debugging on actual devices, so any help would be great.





The really weird part is that it will usually crash when nothing is firing. No touches, no animations, nothing is happening. I've tried running Instruments to check for memory leaks. All I find are two objects that are both created in the menu scene.





I'm changing scenes using







Game *game = [Game nodeWithPlayers:arr Tutorial:NO];

[[CCDirector sharedDirector] replaceScene:game];







which sends some data (mainly # of players) to the Game scene. I put a comment in the dealloc of my menu scene and it fires, so I know that's happening.





The two objects that are reported as memory leaks are my MenuManager object that helps w/ some menu animations and positions in the menu scene, and my SoundManager object which at the moment only plays a couple bit wav file on buttons and a 9mb mp3 as background music. I just don't understand why those objects are even persisting if the menu scene is deallocated...





I'm not sure where to start w/ debugging these seemingly random crashes. Any advice?


Comments

  1. If it doesn't crash on Simulator and the crash is "silent", it seems to be memory overhead. And if you load all resources at once there will be no memory warnings in console.

    Try to run the app with Activity Monitor in Instruments - it measures real memory usage. And try to skip loading textures (inside CCTexture2D class comment glTexImage2D(...).

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex