-
Notifications
You must be signed in to change notification settings - Fork 827
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
#829 Wrap allocation errors in
KryoException
when reading and writi…
…ng fields
- Loading branch information
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
1d72a60
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like fixing a symptom, not the problem.
If you are running OutOfMemory, you probably also don't have the memory to create a new KryoException or the String for the Exception message. You shouldn't catch Errors.
Just guessing: Maybe the issues are the fuzzer settings to not accept Errors?
Or the fuzzer found a condition which was able to trigger OutOfMemory condition (e.g. due to endless recursion)?