On Tue, 28 Oct 2025 20:07:38 GMT, Chris Plummer <[email protected]> wrote:
> I don't see how your changes are fixing the problem described in the CR. The > target process is exiting with an OOME, which shouldn't happen. The OOME is > thrown and caught by ClassUnloader.eatMemory() and should not escape to the > caller. I think your change is good practice for other reasons, but I don't > see it resolving the failure, which I don't think is understood at this point. The OOME fails was observed by ours CI, and I do not repeoduce the OOME fails locally. So I can not verified do this change fix the OOME or not. The OOME was occur after 'GC finish event received', so the OOME do not occur during ClassUnloader.eatMemory(), it should be some where after GC enevt. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28011#issuecomment-3459406973
