OpenSSL and panama-foreign

[Maurizio Cimadamore]

I'm not sure I follow your point entirely.

But yes, if you do a bindTo(this), then using an implicit scope is not 
very useful as long as the scope is reachable from `this`.

We might be able to refine the implementation and improve this in the 
future, but for now I think that's something we have to live with.

Thanks
Maurizio


On 11/11/2021 14:41, Rémy Maucherat wrote:
> Unless I missed something the API has a side effect with upcalls. I
> understand after reading the javadoc where the suggestion comes from,
> as it makes memory management very much like Java. This is of course
> excellent. However, I use upcalls (as you know) and many of them are
> bound to an instance (since this makes state tracking very very nice).
> This however creates a reference that never goes away and an implicit
> scope is never going to get GCed and closed (I saw that with visualvm)
> and memory leaks. Initially I was planning to use a static Map<Long,
> State> for my state (OpenSSL allows passing references and getting
> them in callbacks, but this is a lot handier in C and doesn't make a
> lot of sense in Java), then I found MethodHandle.bindTo actually
> worked and this is quite magical.
>
> So with that in mind, what is the recommendation ? Should the API
> provide a way to remove the MethodHandle upcall ? Or should I avoid
> using bindTo instead ?