On Fri, 19 Dec 2025 06:16:28 GMT, David Holmes <[email protected]> wrote:
>> To ensure JNI critical access to a raw array can't interfere with actions of >> the debugger, we disable JVM TI suspension whilst JNI critical access is >> active, as originally suggested by @fisk. We assume the debugger is being >> operated correctly (ie the thread using the raw array will be suspended), >> and that the critical section is short so as to not delay debugging too >> long. >> >> The mechanism for this already exists courtesy of the virtual thread support. >> >> Testing: >> - tiers 1 - 6 sanity > > David Holmes has updated the pull request incrementally with two additional > commits since the last revision: > > - Delay suspender whilst target is in-critical > - Revert "8373839: Disable JVM TI suspension during JNI critical regions" > > This reverts commit 7723275e4495cc1f514c531afe752210209617cc. Withdrawing this PR whilst a robust solution is sought. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28884#issuecomment-3742167782
