Bug 6227 - Memory Leak
Summary: Memory Leak
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.3.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-07-21 22:28 UTC by nevilleb
Modified: 2013-12-05 18:35 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description nevilleb 2012-07-21 22:28:28 UTC
Please see http://stackoverflow.com/questions/11597098/monotouch-memory-leak for a full description of the issue.

It appears that there is a memory bug somewhere between MT 5.2.12 and MT 5.3.4.
Comment 1 Sebastien Pouliot 2012-07-22 11:19:38 UTC
Hello, I gave a few details on SO but it would be helpful if you could attach a self-contained test case that shows the issue. You can mark it as 'private'.
Comment 2 nevilleb 2012-07-26 23:01:53 UTC
Hi Sebastien,

I have updated the SO page:

I added more detailed code tracing the lifecycle of unpackedImage.
Comment 3 Sebastien Pouliot 2012-08-07 22:11:26 UTC
I could not duplicate the issue with the code from SO. It might be a code "adaptation" adaptation issue or it could have been fixed since 5.3.4 was released.
Comment 4 PJ 2013-11-19 17:05:29 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 PJ 2013-12-05 18:35:53 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.