Jonathan Magnan

Hello @kller1993 , Since our last conversation, we haven't heard from you. How is everything going? Let me know if you need further assistance. Best regards, Jon

Hello again, A simple reminder that we are here to assist you. Don't hesitate to contact us if you need anything. Best regards, Jon

Hello @void80 , Thank you for reporting. Your suspicion is probably 100% right. I remember we fixed a similar issue recently but slightly different #154 (he wanted to cast it...

Hello @strohhaecker , @void80 A new version, `v6.1.7`, has been released today. All known cases we found have been fixed in this issue. Could you test the latest version and...

Thank you @void80 for reporting. Indeed, we only added the logic for the `minus` sign, never for the `plus` sign. We will see if it is worth doing a similar...

Hello @void80 , The v6.1.8 has been released. We added an identical logic to the `plus` sign that we did with the `minus` sign. Let me know if this time...

Hello @P9avel , Unfortunately, no, our library is made to run code at runtime. It doesn't allow you to step through the code as you can easily do with Visual...

Hello @schuettecarsten , The `IncludeOptimized` feature uses the `QueryFuture` to execute his queries. We can see that a `ConditionalWeakTable` is used on this line: https://github.com/zzzprojects/EntityFramework-Plus/blob/master/src/shared/Z.EF.Plus.QueryFuture.Shared/QueryFutureManager.cs#L61C35-L61C139 So, if the context is...

Hello @schuettecarsten , Thank you for the info, so there is a huge chance that the memory leak is due to the `ConditionalWeakTable` as the `DbContext` is never really released....

Hello @viniciusverasdossantos , Do you think you could create a runnable project with the issue? It doesn’t need to be your project, just a new solution with the minimum code...