Crash on Serialization

this little fellow caused the default Serializer to first freeze vvvv and then crash after a couple of seconds.
Only a simple custom serializer for the only field I needed resolved the issue, I’m still left in the dark about what’s causing the original error.


Custom Serializer to resolve the issue:

Windows Event Viewer only helping this much:
Faulting application name: vvvv.exe, version: 38.2.4187.0, time stamp: 0x5d4e7131
Faulting module name: clr.dll, version: 4.7.3416.0, time stamp: 0x5cabfc63
Exception code: 0xc00000fd
Fault offset: 0x000000000006c9b2
Faulting process id: 0x3190
Faulting application start time: 0x01d5582733ee7e6e
Faulting application path: C:\Repositories\projectname\core\vvvv_50alpha38.2_x64\vvvv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: bd7b6b80-29b2-4796-9290-e4e4aca42914
Faulting package full name:
Faulting package-relative application ID:

Crash is obviously bad, but would need a patch to reproduce. I guess it’s related to the default serializer trying to serialize those Editor/TClient/Observable fields while it’s only about the one boolean flag as seen in your custom serializer. So attributes (proof of concept was already working on LINK) would help here and yes better error reporting, but to get at the bottom of that like I said I need the patch.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.