Note that there are some explanatory texts on larger screens.

plurals
  1. POUIKit Memory Leak
    primarykey
    data
    text
    <p>I just used Instrument to check for memory leaks in my app on an iPhone 3G running iOS 3.1.2. I found that there are several leaks displayed in Instruments. The Instruments output is as follows:</p> <pre><code>Leaked Object # Address Size Responsible Library Responsible Frame GeneralBlock-16 2 &lt; multiple &gt; 32 UIKit -[UIViewAnimationState animationDidStart:] GeneralBlock-16 2 &lt; multiple &gt; 32 UIKit -[UIViewAnimationState animationDidStart:] GeneralBlock-16 0x163be0 16 UIKit -[UITransitionView _didStartTransition] GeneralBlock-16 0x160730 16 UIKit -[UITableView(UITableViewInternal) _sectionHeaderViewWithFrame:forSectionpaque:reus eViewIfPossible:] GeneralBlock-16 0x157060 16 UIKit -[UIScrollView(Static) _startTimer:] GeneralBlock-16 0x148480 16 UIKit -[UIScrollView _endPanWithEvent:] GeneralBlock-16 0x13d570 16 UIKit -[UINavigationBar pushNavigationItem:] GeneralBlock-16 0x13c8b0 16 UIKit -[UIScrollView _updatePanWithStartDelta:event:gesture:ignoringDir ectionalScroll:] GeneralBlock-16 0x132240 16 UIKit -[UINavigationTransitionView transition:fromView:toView:] GeneralBlock-16 0x126ec0 16 UIKit -[UINavigationBar popNavigationItem] GeneralBlock-16 0x11ad50 16 UIKit -[UITableViewCell _saveOpaqueViewState:] </code></pre> <p>Because most of the leaked objects come from UIKit (the responsible library reported by Instruments), I'm not sure whether or not I need to clear them, or if it even makes a difference. Are the leaks a serious issue? If I must fix them, how would I do that? I cannot find the trace because the responsible library is not mine.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload