Closed rummelsworth closed 6 years ago
On first taught I would say that it is a bug in Mono. It seems to occur in the DynamicCompiler of Jace. In this component MSIL is generated at runtime to create a delegate. This is less used feature of .NET so maybe the Mono implementation contains bugs. I assume you do not have the issue when you use Jace in interpreted mode on Mono?
Would you be willing to create a bug ticket for the Mono team and share the link here for follow-up?
I've never seen the assertion message occur in the interpreted mode sections.
Here's the link to the Xamarin Bugzilla filing:
With a freshly downloaded and cleanly built Jace.NET solution (https://github.com/pieterderycke/Jace/commit/2c0033aac56dba919a97db8d2a2702b95c9baf1e) and using Mono 3.2.8 on Lubuntu 14.04, running the Jace.Benchmark project causes a crash of some sort during the last "Compiled Mode" section just after the threads are started. Reliably reproducible for me.
Here is a transcript of the application output, including assertion failure message and stacktrace: