RFR: 8026789 Update test/java/lang/instrument/Re(transform|define)BigClass.sh test to use NMT for memory leak detection
Staffan Larsen
staffan.larsen at oracle.com
Fri Oct 18 04:30:06 PDT 2013
Not all platforms support the 'detail' level of Native Memory Tracking. That level isn't strictly necessary for the test in my fix below, but provides more data when an error happens. I have change the test to only use 'detail' when it is supported by the JVM, otherwise I fall back to 'summary'.
updated webrev: http://cr.openjdk.java.net/~sla/8026789/webrev.01/
Thanks,
/Staffan
On 17 okt 2013, at 20:30, Staffan Larsen <staffan.larsen at oracle.com> wrote:
> The two tests currently use /proc/self/stat to read the virtual memory usage for the process. This only works on linux and only gives a single value to analyze. NMT works on all platforms and gives a lot more detail about where the memory is consumed.
>
> Without this fix, I can repro JDK-8023201 when stressing the machine heavily, but with this fix the test passes. The reason for this is probably that NMT uses a more granular measurement of committed memory, and not that the VM actually uses less memory. I have retained the memory growth limit of 32MB, but if that is a good value or not, I don't know. When stressing the test, I see NMT reporting about 1MB in committed memory growth.
>
> I have also removed the tests from ProblemList.txt.
>
> webrev: http://cr.openjdk.java.net/~sla/8026789/webrev.00/
> bug: https://bugs.openjdk.java.net/browse/JDK-8026789
>
> Thanks,
> /Staffan
>
More information about the serviceability-dev
mailing list