Set max stack size in bytebuddy exception handler#256
Merged
Conversation
realark
force-pushed
the
ark/exceptionhandler_stack_size
branch
from
dab30ad to
5ffd214
Compare
Merged
tylerbenson
approved these changes
Mar 7, 2018
Contributor
|
Nice catch! |
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
2 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.
Found the root cause of the verifyerror we've been seeing lately.
Our ExceptionHandler was using
StackSize.SINGLE, which set its max size to 0. This caused a verifyerror in cases where the original stack was less than 3 (the max stack size of our handler).