You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JMH test is currently running without any leak detector levels.
Now, in the old version, tests were run for each leak detector levels, so it would be nice if we could do the same for the new version.
But there is a work around: If you want to enable any leak detector levels, you must then recompile the benchmark and adapt the @fork annotation with some custom jvm options:
@Fork(jvmArgsAppend = {"-dsa",
"-da",
"-XX:+HeapDumpOnOutOfMemoryError",
"-XX:+UnlockDiagnosticVMOptions",
"-XX:+DebugNonSafepoints",
"-Dio.netty5.leakDetection.level=disabled", // changed to paranoid for detecting buffer leaks
"-Dio.netty5.buffer.leakDetectionEnabled=false", // changed to true for detecting buffer leaks
"-Dio.netty5.buffer.lifecycleTracingEnabled=false" // changed to true for detecting buffer leaks
})
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g. java -version)
OS version (e.g. uname -a)
The text was updated successfully, but these errors were encountered:
Expected behavior
JMH test is currently running without any leak detector levels.
Now, in the old version, tests were run for each leak detector levels, so it would be nice if we could do the same for the new version.
But there is a work around: If you want to enable any leak detector levels, you must then recompile the benchmark and adapt the @fork annotation with some custom jvm options:
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g.
java -version
)OS version (e.g.
uname -a
)The text was updated successfully, but these errors were encountered: