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 44170 on
GitHub or 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 17409 [details]
The runtime has problems with generics at a depth of 3. Int64 seems to be working just fine. See the test case attached.
I'm running Mono 4.4.1 (Nightly 126.96.36.199/4747417 Thu Jul 14 18:06:32 UTC 2016) on Arch Linux (up-to-date).
When compiled with csc/msc and ran against Microsoft .Net, the test case produces "foo\nbar". (expected behavior)
When compiled with csc/msc and ran against Mono, the test case produces "foo" and then crashes with SIGABRT:
System.Int64 doesn't implement interface System.Collections.Generic.ICollection<System.Collections.Generic.IList<System.Collections.Generic.IList<System.Int64>>>
at <unknown> <0xffffffff>
at Program.Program.Main (string) <0x00081>
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0x000c8>
Debug info from gdb:
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
Aborted (core dumped)