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 for Bug 59163 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
Created attachment 24510 [details]
Use the Forms Previewer in a way that results in a native crash, in the Java process when previewing.
You might think such crashes are rare, but here are two scenarios that cause them that I found:
And likely there are others.
Anyway, once the layoutlib java process crashes, we relaunch it with custom controls disabled.
After that, when the user tries to preview other Forms pages they just showing a solid grey rectangle with the text XFPageRenderView. See attached screenshot. Every future previewed Forms page will show that, even in different solutions, until the IDE is restarted.
For the native Android designer, disabling custom controls makes sense, so if a custom control causes a crash you can at least see non-custom controls.
But for the Forms previewer everything is a custom control so a mode where they are disabled provides no value to the user. For the Forms previewer it would be better to never go into this "custom controls disabled" mode,
instead just relaunching the the previewer on crash in the normal mode. That way, subsequent pages that crash will still crash, showing an error which is fine, even desirable, but all other pages will display OK.
I would love to include this in d15-4 but unfortunately even if a fix were available today we would not be allowed to include it.
However we should attempt to improve this for d15-5.
Alan, I'm moving this to 15-6 unless you tell me this is fixed and ready to go today.
We don't have fix but we should still endeavour to include one!
None of the fix options possible in 15.5 look very attractive here. Pushing to 15.6.