jb/retained heap analysis #89
Open
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
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.
It shows the amount of memory that would be freed if all references to a particular object removed and it were garbage collected, called the retained size. This would allow us to figure out what/why objects are being held onto and how to fix it. The output is a dominator tree of memory usage starting from the memory roots and sorted at every level by retained memory size. It is shown in XML so that you can collapse and expand introspection. It shows the retained size and the static shallow size for each object. The api is heap-dominator-tree (filename:String) which takes a filename for the xml file that is created and populated with the results.