I'm trying to generate a phash for an image. Unless I'm missing something, the img_hash module is not integrated into the JavaCV lib. Is there a way of doing that?
Thanks!
Marking as duplicate of https://github.com/bytedeco/javacpp-presets/issues/319
Contributions welcome!
I've just added it in commit https://github.com/bytedeco/javacpp-presets/commit/fdc7008402da3a985cad23993986fd17fc0370dd
Please try it out with the snapshots: http://bytedeco.org/builds/
The snapshot works great, thank you!
When is it going to be released?
Probably before long... Thanks for testing out the snapshots!
Having issues with the snapshot repo (it seems to be flakey). Is there an ETA on the release?
Did something break with the latest binaries?
No. But there are issues with availability when maven tries to download the
jar from the snapshot repo.
On Tue, Mar 20, 2018 at 3:11 PM Samuel Audet notifications@github.com
wrote:
Did something break with the latest binaries?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bytedeco/javacv/issues/933#issuecomment-374591692,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEfrVtpCp4qOXxnJMgL-wfS6WI10ujHyks5tgQAJgaJpZM4SgNNQ
.
Released! Enjoy
Hey,
It seems I'm getting this error now:
java.lang.OutOfMemoryError: Cannot allocate new BytePointer(62063): totalBytes = 16, physicalBytes = 1G(Cannot allocate new BytePointer(62063): totalBytes = 16, physicalBytes = 1G)
at org.bytedeco.javacpp.BytePointer.
at org.bytedeco.javacpp.BytePointer.
Caused by:java.lang.OutOfMemoryError: Physical memory usage is too high: physicalBytes = 1G > maxPhysicalBytes = 989M(Physical memory usage is too high: physicalBytes = 1G > maxPhysicalBytes = 989M)
at org.bytedeco.javacpp.Pointer.deallocator(Pointer.java:576)
at org.bytedeco.javacpp.Pointer.init(Pointer.java:121)
at org.bytedeco.javacpp.BytePointer.allocateArray(BytePointer.java:-2)
at org.bytedeco.javacpp.BytePointer.
I'm not sure if I got that with the snapshot. Are you familiar with this type of error?
Just increase the java -Xmx option, it will take care of that.
Yes, but by how much? I'm handling up to 50 images concurrently. And have
seen this error for small images. Is 1G of memory allocated for each and
every image?
On Tue, Apr 3, 2018, 5:18 PM Samuel Audet notifications@github.com wrote:
Just increase the java -Xmx option, it will take care of that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bytedeco/javacv/issues/933#issuecomment-378265953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEfrVnp3V4xlWuAbHxHMM6TOR88MkpW3ks5tk4SYgaJpZM4SgNNQ
.
As much as it needs, probably not 1 GB per image.