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 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.
The fix in #15040 comment 14  needs to be applied everywhere in our codebase otherwise we can experience the exact same crash  in every other place we use ThreadHelper.Invoke, which is currently about 26 places.
Just so there is no ambiguity, here is the relevant section from the documentation link:
This method uses an RPC message to marshal to the UI thread. This will allow the marshaled delegate to execute on the UI thread while the UI thread is already busy executing a previous message. This tends to introduce reentrancy, hangs and crashes, and therefore should be avoided if possible.
This manifested itself exactly as described in the documentation, triggering bug #15040.
I believe there is no way your work will land for 1.6, moving to 1.8.
Plan is to put on 1.8 and back port to 1.6.
This is now applied in 1.6. Over to you Alan with the 1.8 side of things.
1.8/master was fixed several days ago. Closing this.