* Profile https://github.com/rolfbjarne/TestApp (most likely any app can be used) with Instruments, use the Leaks template.
* Leaks: http://screencast.com/t/IZAQTE2jbxA
Fixed in mono master.
Looks like this is not yet in 7.0.6, so it will be included the next time the mono is bumped to master (or a new branch made from master).
It doesn't look like the issue is fully resolved though. I'm still getting plenty of leaks with master. I'm not sure if it's in the gsharedvt code, but I figured I'd provide the results.
184.108.40.206 (aed2b17): http://screencast.com/t/wwi0Phqje
I can reproduce those remaining leaks with master as well.
Fixed in mono 26ac16318df0c83e099c85388d48f37bd53e80ad/mt 189698e2e353176cc15a87e6cd60d110f772890a.
I have checked this issue with latest builds and I am still getting memory leak with attached sample 'TestApp'.
=== Xamarin Studio ===
Version 4.2.4 (build 32)
Installation UUID: b1fc3b76-cf00-405e-a0a1-3839ac11fe6d
Mono 3.2.7 ((no/40f92d5)
GTK+ 2.24.23 (Raleigh theme)
Package version: 302070000
=== Apple Developer Tools ===
Xcode 5.1 (5051.4)
=== Xamarin.Mac ===
=== Xamarin.iOS ===
Version: 220.127.116.11 (Enterprise Edition)
Build date: 2014-03-18 18:20:49-0400
=== Build Information ===
Release ID: 402040032
Git revision: a160c35dac9ab9fd32eeadaa171216316d5a5133
Build date: 2014-03-12 13:55:08-04
Xamarin addins: a779416ceabd54981ce812771a4061c942e8b872
=== Operating System ===
Mac OS X 10.9.3
Darwin Apples-iMac.local 13.2.0 Darwin Kernel Version 13.2.0
Tue Mar 11 22:16:58 PDT 2014
Those are other memory leaks, they are not related to this bug.
@Saurabh like Zoltan in comment #8 said that's a different issue (not a regression, the original gsharedvt memory leak is fixed) and needs a separate bug report (you can give a link to this so the same app/screencast can be re-used).
note: re-opening bug should only be done for regressions (not for similar. but unrelated, issues)
As in comment8, Zoltan said that Comment7 is a different issue. So I have file a new issue for the same:
As per comment 8, comment 9 and comment 10, this issue is fixed and now we are getting different issue so we have filled Bug 18509.
Hence closing this issue.