Viktor Szathmáry
Viktor Szathmáry
Yes, seems to work the other way around.
If there was a way to avoid using Unsafe access to ByteBuffers (pushing the address manipulation to the JNI native layer), it would make it easier to adopt this library...
There's also another obvious option: implement ByteBuffer creation in JNI native code. Of course this would complicate the binding code, but it does not rely on the hacks that are...
On a related note, JDK9 introduced the [`--permit-illegal-access` global flag](http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-March/011763.html), which makes it easier to trace offending code.
`@JsonUnwrapped` also does not work for deserializing properties in `record` classes, since those are final.
@cowtowncoder any suggestions on a workaround to make `@JsonUnwrapped` work with `record` classes?
@cowtowncoder can I offer any help in fixing this bug?
+1 for this. Since `axisPair` is not visible, there's no straightforward workaround for this.
Would love to see this implemented...
I can confirm this leak, we also have a growing number of "can't identify protocol" open sockets, until the FD limit is hit.