|
As in JNI accessed native code cant lock down JVM allocated memory.
If I take that literally, I don't see it as a big deal. If the Java code can lock down the memory before calling down the JNI then it's still fine. I don't see why JNI should ever be allowed to lock JVM memory. Or are you saying that it's now not possible to pin memory at all? I can't imagine that's true. How the heck would JNI work? To the best of my knowledge, this is also how .NET works. If you want to pin memory you must do it in managed code and then you can pass the pointer. The unmanaged code can't randomly pin managed code memory. -Walden
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.