This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 211
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[XDK] Add in-depth allocation tracker
This patch includes in-depth allocation tracker and extention of protocol.json by stackEntryLine that is used for total time annotations in CPU profiling. Details of HeapProfiler: Three new commands were added by analogy with Chrome DevTools allocation tracker. Start/Stop and Event which is sent by timer. Command stopTrackingHeapXDK accepts three parameters: stack depth for unwinding, Sample After Value - period of timer and a flag to collect retention information or not. Event sends to the host currently collected data about symbols/callstack/objects. Command stopTrackingHeapXDK returns the final info witch is similar to Event passed format with one more parameter: duration of the collection. Basing on this info consumer can build allocation call tree for any period of time, annotate source by self and total allocation mertics and annotate allocation call tree by the objects, which retain other objects in the memory.
- Loading branch information
Mishenkov Sergey
authored and
Raphael Kubo da Costa
committed
May 16, 2016
1 parent
34b9287
commit e1bd830
Showing
8 changed files
with
258 additions
and
1 deletion.
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
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
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
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
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
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
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
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