Add BREAKPOINT_VALUE_MEMORY_LIMIT#18
Merged
Merged
Conversation
catalinnnn
approved these changes
Feb 22, 2022
andrei-marinica
approved these changes
Feb 22, 2022
dorin-iancu
approved these changes
Feb 22, 2022
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
4 participants
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.
This PR changes the breakpoint value set by
OpcodeControlwhen too manymemory.growopcodes are run. Previously, the breakpoint value was set toBREAKPOINT_VALUE_EXECUTION_FAILED, now it'sBREAKPOINT_VALUE_MEMORY_LIMIT. This way, the VM can distinguish between a generic failure and a failure caused by over-allocation of WASM memory.