Ensure rss_limit_mb is set to 0 for all Chromium/Google tasks - #5466
Open
tbantikyan wants to merge 1 commit into
Open
Ensure rss_limit_mb is set to 0 for all Chromium/Google tasks#5466tbantikyan wants to merge 1 commit into
rss_limit_mb is set to 0 for all Chromium/Google tasks#5466tbantikyan wants to merge 1 commit into
Conversation
Bug: crbug.com/555763447 In order to ensure that no memory limit is present for our fuzzing engines, the `rss_limit_mb` flag must be set to 0. This was not being done for corpus pruning tasks and for testcases that were manually uploaded.
tbantikyan
force-pushed
the
ensure-no-memory-limit
branch
from
September 14, 2026 14:20
49f4eef to
be55e5d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug: crbug.com/555763447
In order to ensure that no memory limit is present for our fuzzing engines, the
rss_limit_mbflag must be set to 0. This was not being done for corpus pruning tasks and for testcases that were manually uploaded.