aboutsummaryrefslogtreecommitdiff
path: root/bazel/fuzz_target.bzl
diff options
context:
space:
mode:
authorFabian Meumertzheim <meumertzheim@code-intelligence.com>2021-05-05 12:09:32 +0200
committerFabian Meumertzheim <fabian@meumertzhe.im>2021-05-07 16:38:22 +0200
commitf1c4bb507733710bbf292e474e173fcd0d6e8ff5 (patch)
tree1f4acc7f6380454b3965183e3937ce9a1635753d /bazel/fuzz_target.bzl
parentcca74efb030f4bfe941decd218bdfb489f490523 (diff)
downloadjazzer-api-f1c4bb507733710bbf292e474e173fcd0d6e8ff5.tar.gz
Ensure default -Xmx value is below -rss_limit_mb
libFuzzer defaults to an rss_limit_mb of 2048, but we start the JVM with -Xmx4096m. This can lead to libFuzzer OOM reports when a single allocation in Java exceeds 2 GB but still fits into the JVM heap. This is solved by letting the JVM heap size default to slightly less than 2 GB. This change is not fully backwards compatible, but will only cause targets to crash more often than they used to.
Diffstat (limited to 'bazel/fuzz_target.bzl')
-rw-r--r--bazel/fuzz_target.bzl2
1 files changed, 0 insertions, 2 deletions
diff --git a/bazel/fuzz_target.bzl b/bazel/fuzz_target.bzl
index 9f2fe2d5..d802fb42 100644
--- a/bazel/fuzz_target.bzl
+++ b/bazel/fuzz_target.bzl
@@ -63,8 +63,6 @@ def java_fuzz_target_test(
"$(rootpath %s)" % driver,
"--cp=$(rootpath :%s_deploy.jar)" % target_name,
"--agent_path=$(rootpath //agent:jazzer_agent_deploy.jar)",
- # Should be bigger than the JVM max heap size (4096m)
- "-rss_limit_mb=5000",
] + additional_args + fuzzer_args,
data = [
":%s_deploy.jar" % target_name,