Entity Framework - closure of Object Contexts

Question

After using EFProfiler (absolutely fantastic tool BTW!) for profiling a few of our Entity Framework applications, it seems that, in most cases, all of the Object Contexts are not closed.

For example, after running it locally, EF Profiler told me that there were 326 Object Context's opened, yet only 1 was closed?

So my question is, should I worry about this? Or is it self-contained within Entity Framework?

Superabundant

+1 for caring what EF is ACTUALLY doing! – Hullo

Answer 1

If you're not using an IoC container is there anyway you can close the ObjectContexts manually after each request, for example in the End Request of your Global.asax, thereby simulating a "per request" lifestyle for your contexts?

Yuki

Answer 2

ObjectContexts will be disposed eventually if your application is not holding onto them explicitly, but in general, you should try to dispose them deterministically as soon as possible after you are done with them. In most cases, they will hold onto database connections until they are disposed. In my current web application, we use an IoC container (Autofac) to ensure that any ObjectContext opened during a request is disposed at the end of the request, and does not have to wait for garbage collection.

Envoy

Answer 3

I suggest you do worry about it and try to fix the issue as Object Contexts are pretty "bulky". If you have too many of them your application may eventually end up using more memory than it needs to and IIS will be restarting your application more frequently then...

Haitian