You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code should execute successfully as engine1 is disposed before engine2 is created.
Instead the result is an InvalidOperationException with the message The single REngine instance has already been disposed of (i.e. shut down). Multiple engine restart is not possible.
This is occurring because the internal engine field within REngine is not being set to null during the Dispose(bool disposing) method.
Is this by design?
As a workaround, I am treating REngine as a singleton within my application but I believe I should be able to dispose and recreate it repeatedly.
My issue is occurring within an Azure Function that wraps an R library and loads an REngine for each request for isolation between calls.
The text was updated successfully, but these errors were encountered:
I am using R.NET 1.9.0 with .NET Framework 4.8 and R 4.1.0.
Given the following code:
This code should execute successfully as
engine1
is disposed beforeengine2
is created.Instead the result is an
InvalidOperationException
with the messageThe single REngine instance has already been disposed of (i.e. shut down). Multiple engine restart is not possible.
This is occurring because the internal
engine
field withinREngine
is not being set tonull
during theDispose(bool disposing)
method.Is this by design?
As a workaround, I am treating
REngine
as a singleton within my application but I believe I should be able to dispose and recreate it repeatedly.My issue is occurring within an Azure Function that wraps an R library and loads an REngine for each request for isolation between calls.
The text was updated successfully, but these errors were encountered: