fix: Set memory limit for javap #4141
Merged
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.
Description
The start.sh script didn't provide a configuration for heap memory in the call of the
javap
application. It means the default values were taken (1GB). The requirement is 3MB with JDK8 and JDK17. This PR sets 4MB as the initial size and 16 MB as the maximum.The omitted configuration could generate an issue with the system with limited resources, and in the same way, it is not necessary to allocate so much memory for this command. It is just to check what version of Java is in use.
Linked to # (issue)
Part of the # (epic)
Type of change
Please delete options that are not relevant.
Checklist:
For more details about how should the code look like read the Contributing guideline