-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Infinite loop in compiled query cache #7230
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
@anpete please investigate and see what releases this applies to. |
anpete
added a commit
that referenced
this issue
Jan 7, 2017
Ensure we let waiting threads proceed when query compilation fails.
anpete
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Jan 12, 2017
Fixed in rel/1.1.1 |
This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done. |
@anpete closing again since the fix is in and approved for the patch. |
verified |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
After a while of usage, my ASP.NET Core API gets stuck at 100% CPU and needs to be restarted. By the way I've found my Azure App Service stuck at 100% CPU after 24+ hours, I'm just guessing it's infinite ;)
I would appreciate any pointers or tips as to what I can do/give to help diagnose further.
It's hard to tell exactly where the loop is occurring, but when I break execution, the call stack looks very much like this:
http://imgur.com/a/oKst0
(Lots of recursive
ExpressionEqualityComparer.GetHashCode
underCompiledQueryCache.GetOrAddQueryCore<>
)Edit: Bonus - in trying to repro this, I see an exception when calling those endpoints below. I don't know why this would occur sometimes, and other times the code gets stuck in a loop.:
Steps to reproduce
Same model as #6937, #6938, #7102.
The two queries sitting somewhere in the call stacks are (
note - I can't be sure it's these ones in particular causing itI've confirmed these were the methods causing my problem by re-ordering the LINQ clauses and not having the problem since):and
Further technical details
EF Core version:
1.2.0-preview1-22878
Database Provider:
Microsoft.EntityFrameworkCore.SqlServer
Operating system: Window 10.0.14393
IDE: VS2015, commandline, Azure App Service
The text was updated successfully, but these errors were encountered: