-
Notifications
You must be signed in to change notification settings - Fork 35
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
Memory leak detected. #46
Comments
Hello. Could you please provide a few examples that reproduce the problems reported? This would help to better understand the underlying issues with the bindings.
|
Sry for reply so late. @Enet4 Here is an example code. Mock as a server, its memory will raises rapidly from 2M to 10+G and without upper bound.
|
This seems as a issue about memory leak in search case. |
Hello,
I use the crate-0.10.0 for our embedding recall, and have found some tips:
a. IndexImpl has not impl concurrentIndex, so IVFScalarQuantizerIndexImpl returned by into_ivf_scalar_quantizer builds error;
b. search increase the leaking of memory without upbound limit, so does the read_index, dropped but no release the RES memory.
What would the problem be? Anybody encount?
Thanks
The text was updated successfully, but these errors were encountered: