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.
does it work correctly without sgen ?
That might explain why we had issue duplicating it.
RosyWriter App builds successfully when sgen is disabled
Application Build Output: https://gist.github.com/GouriKumari/64a9809696bd6be63d00
*** Bug 13118 has been marked as a duplicate of this bug. ***
There's no need to make this one a blocker. From bug #13118:
> Likely not a big, immediate deal since we'll switch to mono-3-2 branch for the
> RC / 6.4 release.
That issue is newer than what we'll be using on the mono-3-2 branch.
Changing to critical / post-async.
Ah ok. Once we get the RCs we will confirm. If it's still there on the RC we'll have to REOPEN, but otherwise this is fine for 6.4.x
Or not REOPEN, sorry, but re-set the severity to blocker.
Sure, I tested it myself but I definitively *want* you guys to confirm it :-)
Is this issue fixed?
RosyWriter builds with sgen for devices, (if you want to see it, http://screencast.com/t/FqyNS8VJanYi)
monotouch-test passes on devices with sgen enabled: https://wrench.internalx.com/Wrench/WebServices/Download.aspx?workfile_id=1306493
It seems as though either the workaround was added to master or we got the fix in for real. VERIFYING as FIXED.
Sorry to have omitted this initially. The build used to verify in comment 10 was:
Mono 3.2.0 7c7fcc7