Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmark does not use leak detector levels #8

Open
pderop opened this issue Aug 22, 2022 · 0 comments
Open

Benchmark does not use leak detector levels #8

pderop opened this issue Aug 22, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@pderop
Copy link
Collaborator

pderop commented Aug 22, 2022

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:

@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)

@pderop pderop added the enhancement New feature or request label Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant