Memory leak in FieldResolver
See original GitHub issueNEST 2.0+:
If Nest.Field
was created by LambdaExpression
then MemberExpression.GetHashcode()
used as Hashcode for dictionary FieldResolver.Fields
, but method GetHashcode
has not overridden in MemberExpression
and used Object.GetHashcode()
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Issue #449 · MichalLytek/type-graphql - Memory Leak
Describe the bug We are facing a memory leak issue. We have a graphql query that returns 1200 records and called every 10...
Read more >[Client Core Developers] Possible memory leak in ...
=> First thing I would try in your case is to trigger manual garbage collection, just to see if memory usage is going...
Read more >Having trouble tracking down Node JS memory leak
Here is what we have attempted to do to resolve this leak: Use PM2 max-memory-restart parameter to force a restart before we run...
Read more >How can I debug a memory leak on my Apollo GraphQL server?
You could user node-memwatch to detect where is memory leak. It also might be a known issue, here is the link with a...
Read more >Migrating from v4.x to v5.x
Memory leaks have been eliminated in the case of errors, output extensions, metrics being enabled, or the use of the context's array pool....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
👎 us first for missing the issue when initially reported and second for introducing this in the first place 😢
We will get this fixed today and put an update out on nuget.org
Just pushed new versions of Elasticsearch.Net and NEST to nuget with a fix for this.
Thanks again for reporting 👍