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.
Seeing this suspicious managed exception very occasionally. I am only seeing this so far on tests which also are frequently failing for other reasons. I am only seeing it so far on ARM64.
System.Runtime.Serialization.SerializationException: The constructor to deserialize an object of type 'System.DelegateSerializationHolder' was not found. ---> System.Runtime.Serialization.SerializationException: The constructor to deserialize an object of type 'System.DelegateSerializationHolder' was not found.
at System.Runtime.Serialization.ObjectManager.GetConstructor (System.RuntimeType t) [0x00029] in <8a9a5589b31145e380f013e432f5ec17>:0
at System.Runtime.Serialization.ObjectManager.CompleteISerializableObject (System.Object obj, System.Runtime.Serialization.SerializationInfo info, System.Runtime.Serialization.StreamingContext context) [0x00034] in <8a9a5589b31145e380f013e432f5ec17>:0
--- End of inner exception stack trace ---
I am looking at an issue with Zoltan where GCC optimizations are storing pointers in ARM64 FPU registers and we are not scanning those, leading to memory corruption and segfaults. This crash seems to only occur on the same tests where the FPU crashes occur, so maybe it is a symptom of the memory corruption problem.
I believe this is fixed by https://github.com/mono/mono/pull/4127 and can be closed