Query cache (eviction) changes between 2.2.6 and 3.0 (preview 8)

[mvacha]

We are investigating a memory leak in our app, that occurs with EF 2.2.6, but no longer happens in 3.0-preview 8. It seems similar to #13513, but I haven't been able to find any merge request that would be fixing this issue, or a PR implementing cache eviction that had been merged to 3.0 (e.g. some follow-up PR of #13021).

Have there been any changes in how caching of queries work in 3.0 (or updates on: #12905)? Thanks.

[ajcvickers]

@mvacha The internals of the query pipeline have been extensively changed for the 3.0 release. As part of this several bugs in query/compilation caching have been fixed, although it is hard to isolate these to specific PRs. That being said, nothing has explicitly changed in cache eviction itself. Given that you are no longer seeing the memory leak it seems likely that the architecture change fixed the issue you are seeing on 2.2, so closing this for now.

[mvacha]

@ajcvickers Thank you for your response. We mitigated the issue in 2.2.6. by using parameterized queries and splitting large EF queries into multiple ones. Since it is fixed in 3.0, I assume it does not make sense for us to investigate what particularly caused it as 2.2. won't be receiving any updates except critical bug fixes in the future, am I right?

[ajcvickers]

@mvacha That's correct.