Bug 48777 - "constructor to deserialize an object of type 'System.DelegateSerializationHolder' was not found"
Summary: "constructor to deserialize an object of type 'System.DelegateSerializationHo...
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-12-02 19:44 UTC by Andi McClure
Modified: 2016-12-20 14:23 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Andi McClure 2016-12-02 19:44:06 UTC
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.

Unhandled Exception:
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 ---

Seen in

MonoTests.sgen-regular-tests-ms-conc-split.sgen-domain-unload-2.exe
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=debian-8-arm64/1329/testReport/MonoTests/sgen-regular-tests-ms-conc-split/sgen_domain_unload_2_exe/

MonoTests.sgen-regular-tests-ms-conc-split.sgen-domain-unload-2.exe
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=debian-8-arm64/1356/testReport/MonoTests/sgen-regular-tests-ms/sgen_domain_unload_2_exe/
Comment 1 Andi McClure 2016-12-09 18:11:13 UTC
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.
Comment 2 Andi McClure 2016-12-09 20:31:23 UTC
I believe this is fixed by https://github.com/mono/mono/pull/4127 and can be closed