Skip to content

chore: remove DumpPerfMapAtExit in favor of custom dumper #295

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.

Sign up for GitHub

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

Merged
not-matthias merged 1 commit into from
Apr 17, 2026
+4 −1
Merged

chore: remove DumpPerfMapAtExit in favor of custom dumper #295

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/executor/helpers/env.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,10 +47,13 @@ pub fn get_base_injected_env(
// - PreserveFramePointer: Preserves frame pointers for profiling.
// - DumpPerfMapAtExit: Writes /tmp/perf-<pid>.map on JVM exit for symbol resolution.
// - DebugNonSafepoints: Enables debug info for JIT-compiled non-safepoint code.
// - EnableDynamicAgentLoading: Suppresses warning when loading JVMTI agents at runtime.
// - jdk.attach.allowAttachSelf: Allows the JVM to attach a JVMTI agent to itself
// (used by codspeed-jvm's perf-map agent for @Fork(0) benchmarks).
if mode == RunnerMode::Walltime {
env.insert(
"JAVA_TOOL_OPTIONS".into(),
"-XX:+PreserveFramePointer -XX:+UnlockDiagnosticVMOptions -XX:+DumpPerfMapAtExit -XX:+DebugNonSafepoints".into(),
"-XX:+PreserveFramePointer -XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints -XX:+EnableDynamicAgentLoading -Djdk.attach.allowAttachSelf=true".into(),
);
}

Expand Down
Loading