Hello,
I want to ask if there is any project that you are working for update the pom file with a java version more stable.
I want to highlight how the use of native access exposes you project at possible memory leak and future issue with the integration with other resources.
These are some related articles :
https://blogs.oracle.com/javamagazine/post/the-unsafe-class-unsafe-at-any-speed
@carlo8767 could you be more specific about where we use unsafe that you’re pointing at or is this just an article you’re spamming across different java forums? In javacpp? We have built in garbage collection and a lot more complex mechanisms than unsafe in the code base. Unsafe is FAR from the only place where we do off heap.
@carlo8767 sorry unless you’re actually going to point to specific code I’m just going to disregard this. Eclipse has a CVE process and I’ve fixed multiple vulnerabilities when users point them out. If you have something more specific to contribute I’m happy to engage. I literally do not use unsafe in the code base so I’m going to just disregard this as generic spam. Sorry if that’s not the response you wanted but you clearly didn’t really do your research.