On Thu, 15 Jan 2026 15:37:58 GMT, Christopher Schnick <[email protected]> wrote:
>> This is a very basic solution to the OOBE described in the issue. While it >> would definitely be better to figure out the root cause, understanding the >> NGNode implementation is above my knowledge level atm. >> >> The code has been like that for 10 years and no one complained, so I am not >> sure whether this is a deeper issue or just a small oversight when handling >> all possible cases. >> >> The fix should retain the exact original workings of the method while >> avoiding the exception. > > Christopher Schnick has updated the pull request incrementally with one > additional commit since the last revision: > > Add comment So I looked into the tests. Even in terms of manual testing, this would still require using a debugger and breakpoints to see if the issues is fixed. I'm not sure whether this could still be considered a manual test if it involves that kind of setup With the reproduction instructions of the linked JBS issue, this should always be testable for someone looking to test whether this fix works. The code from the monkey tester system info window perfectly manages to reproduce it. I updated the reproduction instructions a bit to make it more clear when it happens ------------- PR Comment: https://git.openjdk.org/jfx/pull/2037#issuecomment-3756019642
