-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.NullReferenceException - when known types differ in serialization and deserialization process #188
Comments
System.OutOfMemoryException: 'Exception of type 'System.OutOfMemoryException' was thrown.' Will be thrown if I encapsulate serialized data by TransportObject.
|
I'm sorry, what was the expected vs. actual behavior here? |
In the first case - if well known types differs (imagine client server application where server is already updated and client is connecting to updated server for its update) there should be more polite way to deal with these changes (e.g. hooking some event). In case of "System.OutOfMemoryException" it seems there is some kind of error in memory allocation. I am sorry I should create two threads instead of one. |
The text was updated successfully, but these errors were encountered: