[Mono-bugs] [Bug 566360] New: Memory leak with simple navigation app

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Dec 21 04:01:11 EST 2009


http://bugzilla.novell.com/show_bug.cgi?id=566360

http://bugzilla.novell.com/show_bug.cgi?id=566360#c0


           Summary: Memory leak with simple navigation app
    Classification: Mono
           Product: MonoTouch
           Version: SVN
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Runtime
        AssignedTo: gnorton at novell.com
        ReportedBy: curtis.wensley at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=333650)
 --> (http://bugzilla.novell.com/attachment.cgi?id=333650)
MonoTouch NavigationController app to reproduce issue

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-us)
AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10

With a very simple NavigationController based application, navigating causes
memory to increase, and does not come back down.  This will (eventually) cause
the iphone to start lagging and will become slower and less responsive.

There is probably other situations which cause memory leaks.

Note that a simple navigation app created in xcode/objc does not have this
issue.  I have attached as well for reference.

Reproducible: Always

Steps to Reproduce:
1. Create simple navigation app (one is attached)
2. Attach instruments to app running in simulator
3. Navigate around, then back to root

Actual Results:  
Memory and # of allocated objects steadily increases, but does not go back down

Expected Results:  
Memory should only go up as application is processing, and go back down when in
the initial state (at the root view controller of the nav).

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list