-
Notifications
You must be signed in to change notification settings - Fork 152
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
Bug: Java bindings throws Out of memory error #308
Comments
I've encountered a similar error too |
Thank you, @superkelvint and @ThangTo! Looking into it and will hopefully have a solution tomorrow 🤗 |
## [2.8.12](v2.8.11...v2.8.12) (2023-11-13) ### Docs * Typo in Java README (#307) ([494b9f0](494b9f0)), closes [#307](#307) * Update Java's step-by-step build instructions (#306) ([63d8027](63d8027)), closes [#306](#306) ### Fix * Dumping to uninitialized memory in Java ([9eaa10d](9eaa10d)) * Key type mismatch in Java ([25dc6fc](25dc6fc)) * Normalize bit-vector length for SimSIMD (#311) ([8a77b3e](8a77b3e)), closes [#311](#311) * OOM error in Java ([2589979](2589979)), closes [#308](#308) ### Improve * TypeScript annotations (#309) ([6a5e009](6a5e009)), closes [#309](#309) ### Make * Trace used compiler ([7d17eab](7d17eab))
🎉 This issue has been resolved in version 2.8.12 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
@ashvardanian Thank you for updating to the new version, everything is ok. |
@ThangTo, sure, we can change the Java interface to be more similar to other bindings. Any chance you or @superkelvint could contribute? Thank you! |
@ashvardanian That is currently beyond my ability, I am having difficulty coding C/C++(never coded C/C++ before), can you help me. Haizz |
Describe the bug
Out of memory error with Java bindings.
Steps to reproduce
Follow the Java README code:
throws this error:
Expected behavior
No error occurs.
USearch version
2.8.10
Operating System
Ubuntu 22.04
Hardware architecture
x86
Which interface are you using?
Other bindings
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: