-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[GR-34212] Populate Throwable.stackTrace lazily #6533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
…kTrace and RealLog
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.
This optimizes
Throwable#fillInStackTraceby storing raw instruction pointers (IPs) instead of eagerly populating theStackTraceElementarray. The raw IP backtrace is later decoded inStackTraceElement#of(Object, int)(which is called fromThrowable#getOurStackTrace). Since raw IPs are only stable for AOT compiled methods, the optimization is disabled if runtime compilation is enabled. Runtime compilation support is planed for follow-up work.Throwableobjects stored in the image heap are reset and do not hold stack trace information. In case theThrowableobject is writable (seeThrowable#Throwable(String, Throwable, boolean, boolean)), a new stack trace can be constructed by callingThrowable#fillInStackTracemanually.