BindingSpecializer emits some code to deduplicate calls to MemorySessionImpl::acquire0/release0. That is, if multiple address parameters share the same arena, only one call to acquire0/release0 is made.

Unfortunately, the logic for doing this is branchy and involves saving the memory segment sessions into local variable slots of the generated method. This seems to cause some issues with escape analysis if the number of arguments becomes too big.

Reverting to simpler code that does not de-duplicate seems to address the escape analysis woes:

https://github.com/openjdk/jdk/compare/master...mcimadamore:jdk:acquire_scope_escape_analysis?expand=1