Iphone SDK Utility Application template has leak

前端 未结 8 1032
一向
一向 2020-12-06 11:05

i\'m only create an project with a Utility Application template. This template has a native memory leak when i push \"info button\" to flip the view.

Anyone know how

相关标签:
8条回答
  • 2020-12-06 11:22

    Hope this helps.

    From: http://www.cocos2d-iphone.org/forum/topic/2460

    "The simulator has bugs related to singletons and llvm stuff that are incorrectly reported by Instruments. Always check your leaks on the device itself."

    0 讨论(0)
  • 2020-12-06 11:26

    Leaks has flagged open_handle_to_dylib_path in CoreGraphics for me as well; there is definitely something flagged here. Since it is merely 256 bytes at its heaviest, I fired off a bug report to Apple and called it done. You can then set a rule in Leaks' configuration to ignore the report.

    As bbum pointed out, there might be serious voodoo at work. I seriously doubt Apple would let leaky frameworks go through QA -- especially since it's so easy to reproduce.

    0 讨论(0)
  • 2020-12-06 11:26

    I had the same problem, but was able to understand why it happened. And I have given a brief info regarding this problem in this article

    Might be useful for you.

    0 讨论(0)
  • 2020-12-06 11:30

    I tried it on a real ipod touch. No leak was reported. Probably just a simulator thing ...

    0 讨论(0)
  • 2020-12-06 11:30

    In the current SDK utility template is no leak. How did you get the impression there's a leak in the template? It's just allocating memory which is needed for the views.

    A leak is memory to which no pointers exist and which cannot be freed any more.

    0 讨论(0)
  • 2020-12-06 11:32

    That might be a leak or it might not be a leak. If you were to add the backtrace of the allocation, that would be helpful.

    More likely than not, it isn't a leak, but some bookkeeping information that is being stashed away by dyld that leaks/Instruments loses track of.

    Given that it is 128 bytes and I'm guessing there is only one of them, I would encourage you to file a bug via http://bugreport.apple.com and then forget about it for now as, in the unlikely case that it really is a leak, you will be equally as unlikely to be able to fix it from within your application.

    0 讨论(0)
提交回复
热议问题