On Mon, 9 May 2022 21:57:41 GMT, Leonid Mesnik <lmes...@openjdk.org> wrote:
>> A trivial fix to nsk_jvmti_threadByName() to solve a native memory leak. >> >> This fix has been stress tested with my >> StressWrapper60M_NMT_detail_suspendthrd003.java >> test and I did NMT detailed monitoring for the whole 60M run. Total >> committed memory has >> gone down from 1.17GB to 300MB. Prior to my last rebase, it was down to >> 239MB. >> >> I ran the fix thru Mach5 Tier[1-7] with no failures. I just rebased the fix >> to the latest jdk/jdk >> and Mach5 Tier[1-3] have passed with no failures. Tier[45] are still running. > > Marked as reviewed by lmesnik (Reviewer). @lmesnik - Thanks for the review! Do you agree that this is a trivial fix? ------------- PR: https://git.openjdk.java.net/jdk/pull/8609
