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
GitHub or 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.
This is a tracking bug so the test can be disabled so we have green builds again.
The benchmark works with the upstream runtime. I'll re-enable it in the testing suite.
The test leads to a segfault on certain mac x64 machines due to this fragment calling the constructor with incorrect argumetns:
newobj instance void [mscorlib]System.OverflowException::.ctor(string)
The runtime correctly identifies the problem when run with --security=verifiable.
I'll submit a fix for the test case shortly.
Is there an issue with the runtime crashing on that code, though?
Fixed by https://github.com/mono/mono/pull/4927