(0.44) Do not throw in ClassLoaderTable #19146
Merged
Conversation
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
In copyJ9UTF8(), we now avoid throwing std::bad_alloc() if memory for a copy of a ROM class's name could not be allocated. We instead do not add the TR_ClassLoaderInfo into the _nameTable in such situations. This parallels the treatment of the class loader info if a chain for the loader could not be found in the SCC. Signed-off-by: Christian Despres <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In copyJ9UTF8(), we now avoid throwing std::bad_alloc() if memory for a copy of a ROM class's name could not be allocated. We instead do not add the TR_ClassLoaderInfo into the _nameTable in such situations. This parallels the treatment of the class loader info if a chain for the loader could not be found in the SCC.
Related: #18990