Elasticsearch-net: Memory leak in FieldResolver
NEST 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().
alwag85
All 5 comments
+1, this is a critical issue for us
rasmus
on 3 May 2016
Aggreed - this one is sucking up alot of memory on our webservers.
tabro
on 3 May 2016
+1, eating up gigs of memory
krjensen
on 3 May 2016
:-1: us first for missing the issue when initially reported and second for introducing this in the first place :cry:
We will get this fixed today and put an update out on nuget.org
Mpdreamz
on 3 May 2016
👍2
❤1
🎉1
Just pushed new versions of Elasticsearch.Net and NEST to nuget with a fix for this.
Thanks again for reporting :+1:
russcam
on 4 May 2016
Was this page helpful?
0 / 5 - 0 ratings
Related issues
romansp
路
3Comments
maxsel
路
5Comments
ejsmith
路
3Comments
joostvz
路
3Comments
iderbyshev
路
3Comments
Most helpful comment
:-1: us first for missing the issue when initially reported and second for introducing this in the first place :cry:
We will get this fixed today and put an update out on nuget.org