After exporting my game to XCode and then running it on the hardware, I notice my game runs at an unplayable frame-rate and speed. After having XCode analyze the code, 298 errors all related to memory leaks are plaguing my game. The errors themselves seem to be throughout the program and not islolated to any particular area. It is these memory leaks that causing serious slowdown in the program and I'm wondering how to fix them. I looked at the post of how to run faster games but I fear it is more a problem with how the exporter is compiling the code than anything I can fix through MMF2. Please advise if anyone has experienced simmilar problems.
Memory Leak Issues with XCode after iOS export
Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
The only way François/Andos can help is by sending your game file by PM.
-
XCode thinks that we have memory leaks, but in fact we dont. This comes from the way it is programmed and the way XCode wants the allocation/deallocations to be done. If you run MMF in instruments, you will se that the current memory size does not increase (as compared to the <currrent> EDIT, of course I meant total memory size).
But there might be a localised problem with your app. First thing to check : do you pile up objects undestroyed somewhere? -
Still I have to say that several iPhone Apps got some sort of memory leaks and are crashing - Fearie Solitaire after long time being in the background stops responding and crashes during next runtime. Planet Wars is unplayable due to crashes later on in the levels at random places.
-
Well as Francois says there might be a localised problem with the apps... so good idea to see if its a particular set of code groups etc that is crashing it.
-
I'm going to be working on an update to stop those freezes on planet wars in the coming weeks after doing some XNA stuff. They happen the most when a lot of action is happening.
-
Sorry for replying this late in the thread (I've been on holiday).
If you believe you have a game that leaks memory and/or crashes after a while, please send them to me so I can profile them properly and find the leak/cause.
All the games I've profiled so far did not leak any memory but there might be a slight chance that your game does something we have not profiled before.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
