-
-
Notifications
You must be signed in to change notification settings - Fork 832
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
Instantiated services not disposed on exception during IStartable #1392
Comments
Thanks for filing this - it's an interesting edge case. Container creation depends on the I'm guessing we haven't handled this because, in general, if an application's container doesn't successfully build, the application itself is largely unusable. There's no "recovering," so the process terminates and the various finalizers are left to do their work to clean things up rather than actively calling Which isn't to say we shouldn't handle it, just that I can see why no one thought of that as a thing to test. |
From stackoverflow: https://stackoverflow.com/questions/76991305/autofac-dispose-of-created-services-not-called-when-exception-is-thrown-by-late
I have the following, minimal example to reproduce an issue of my real life application:
and a console application:
From dependency chain ServiceB is a dependency of ServiceA and, therfore, is instanciated first on Build(). During Start() of ServiceA, Connect() on ServiceB is called which throws an Exception. The Exception is forwared to Build() which fails and the container is not created.
My expectation reading Autofac docs
would be, that Dipose() on created ServiceB is called. This is not the case. ServiceB lives somewhere in my application and I cannot dispose it as IContainer was not created.
ChatGPT suggest to catch the exception and call Dispose() on IContainer later. This would mean, I need to check if Connect() on ServiceB was successfull (property bool IsConnected) and if not, I call Dispose().
Of course, this would solve my issue. But again, my expecation was, that Autofac is handling this for me via LifetimeScope.
The text was updated successfully, but these errors were encountered: