[Closed] [foreign-memaccess] RFR: Fix concurrent MemoryScope.close() or MemoryScope.dup() race
plevart at openjdk.java.net
Wed May 13 17:03:05 UTC 2020
On Mon, 11 May 2020 22:29:27 GMT, Peter Levart <plevart at openjdk.org> wrote:
> In case a MemorySegment is not confined to an "owner" thread, it is possible to call close() or
> withOwnerThread(newThread) on it from multiple threads concurrently and such calls are not screened for thread
> confinement but just forwarded to MemoryScope.close() and .dup(). It is therefore vital that close() and dup() are made
> atomic so that cleanupAction is executed just once.
This pull request has been closed without being integrated.
More information about the panama-dev