-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Remoting error due to GC issues when using App Domain #28
Comments
If you use AppDomains any objects you use have to be either |
Everything we are using is Serializable. In the past, when we weren't, we got exceptions thrown. |
There's an option Serializable exceptions can occur even if your top level object is serializable, but one of your subobjects isn't. For example, if you have a DateTimeOffset it may break because that class isn't serializable. Or if you have any other non-serializable child objects. You can dig into the exception and the stacktrace to hopefully find out exactly which object is failing to serialize either in the parameter list or the return value. |
@RickStrahl
I think the problem comes from RazorEngineConfiguration : MarshalByRefObject it does not override InitializeLifetimeService method. |
Hmmm... maybe RazorEngineConfiguration should just be |
I'm getting the following error:
System.Runtime.Remoting.RemotingException: Object ‘/76e7cd41_2cd2_4e89_9c03_fae752ec4d59
/zb_uualy_cm6kwizjlentfdl_3.rem’ has been disconnected or does not exist at the server.
It appears to be due to GC issues when using an App Domain. I see where you have a virtual method on the RazorBaseHostContainer called InitializeLifetimeService(). But the Xml Doc seems to indicate that how you have it should keep it alive indefinitely. We are not finding that to be the case.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: