Home/ Questions/Q 6958971
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T15:12:38+00:00

I have a slight problem where when the user plays my game for more

  • 0

I have a slight problem where when the user plays my game for more than 20 minutes or so it begins to slow quite considerably. However I have been trying to work through the issues pretty hard as of late but still no luck. I have tried the leaks instrument and I now have that squared away, but I read at “bbum’s weblog” about using the Allocations Instrument and taking heap shots. But i dont quite understand what i am looking at, could some one give me a hand with this?

My game involves users selecting words. I took a heap shot after each word was selected, but i am not too sure how exactly to read this. Is the heap Growth column what is currently running or is it was has been added to what is currenlly running?

And what is the # Persistent?

Also why is the # Persistent jump so much? Could that be my memory problem?

enter image description here

Thanks for all the help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The heap growth column represents all of the allocations in that iteration that did not exist prior to that iteration but continue to exist in all subsequent iterations.

    I.e. Heapshot 4 shows a 10.27KB permanent growth in the size of your heap.

    If you were to take an additional Heapshot and any of the objects in any of the previous iterations were deallocated for whatever reason, the corresponding iteration’s heapshot would decrease in size.

    In this case, the heapshot data is not going to be terribly useful. Sure; you can dive in an d look at the various objects sticking around, but you don’t have a consistent pattern across each iteration.

    I wrote considerably more about this in a weblog post.

    If it’s slowing down, why not try CPU profiling instead? Unless you’re
    getting memory warnings, what makes you think it’s a leak?

    Tim’s comment is correct in that you should be focusing on CPU usage. However, it is quite effective to assume that an app is slowing down because of increased algorithmic cost associated with a growing working set. I.e. if there are more objects in memory, and those objects are still in use, then it takes more time to muck with ’em.

    That isn’t the case here; your heap isn’t growing that significantly and, thus, it sounds like you have a pure algorithmic issue if your app is truly slowing down.

    • 0