On Thu, 18 Jun 2026 01:18:24 GMT, Chris Plummer <[email protected]> wrote:
>> The PR resolves the issue JDI has with allowing collection of objects that >> are returned by the JDI invoke API before the caller of the API has a chance >> to call ObjectReference.disableCollection(). Details in the first comment. >> >> Consider this to be a prototype. I'm open to discussion on other possible >> solutions. I also still need to update the JDI specs to reflect these >> changes. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Chris Plummer has updated the pull request with a new target base due to a > merge or a rebase. The incremental webrev excludes the unrelated changes > brought in by the merge/rebase. The pull request contains six additional > commits since the last revision: > > - Merge branch 'master' into 8311176_disablegc > Merge > - support WhiteBoxAPI for debuggee > - fix some jcheck whitespace errors > - fix some jcheck whitespace errors > - cleanup some comments > - add support for diabling gc on returned objects I've created draft PR #31586 to cover the "always pin" approach. I also made the ObjectReferenceImpl cache changes I mentioned above (use weak references instead of soft reference and dispose of ObjectIDs sooner rather than waiting for 50 of the to accumulate). ------------- PR Comment: https://git.openjdk.org/jdk/pull/31421#issuecomment-4748405866
