Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 5088 [details]
A project that shows the leak
The method NSData.ToString leaks.
The attachment includes a project that show the leak and a file of XCode Instruments "Memory.trace" that shows an execution of the project. The project has 3 buttons. The first one shows the memory leak. The second proves that is NSData.ToString that generates the leak. The last button proposes a work around I will use for now.
Looks like a refcount issue in manual bindings. Looking into it...
Confirmed, there's an extra retain on the native NSString.
Fixed in 279d54af951722b525c63802877ecb93bf8f40c2
Thanks for providing a test case!