1. 24 Sep, 2019 1 commit
  2. 16 Sep, 2019 1 commit
  3. 13 Sep, 2019 1 commit
  4. 22 Aug, 2019 1 commit
  5. 20 Aug, 2019 1 commit
  6. 09 Aug, 2019 1 commit
  7. 26 Jul, 2019 1 commit
  8. 22 May, 2019 1 commit
  9. 15 May, 2019 1 commit
  10. 13 May, 2019 1 commit
  11. 10 May, 2019 1 commit
  12. 08 May, 2019 1 commit
  13. 25 Apr, 2019 1 commit
  14. 24 Apr, 2019 2 commits
  15. 16 Apr, 2019 1 commit
  16. 03 Apr, 2019 1 commit
  17. 26 Mar, 2019 1 commit
  18. 18 Mar, 2019 1 commit
  19. 13 Mar, 2019 1 commit
  20. 09 Mar, 2019 1 commit
  21. 24 Jan, 2019 1 commit
  22. 09 Nov, 2018 1 commit
  23. 18 Oct, 2018 1 commit
  24. 20 Sep, 2018 1 commit
  25. 14 Sep, 2018 1 commit
  26. 17 Aug, 2018 1 commit
  27. 06 Aug, 2018 1 commit
  28. 12 Jul, 2018 1 commit
  29. 06 Jun, 2018 1 commit
  30. 31 May, 2018 1 commit
  31. 28 May, 2018 1 commit
  32. 23 May, 2018 1 commit
    • Peter Marshall's avatar
      [cpu-profiler] Add a new profiling mode with a more detailed call tree. · ecae80cd
      Peter Marshall authored
      The current profiling mode (called kLeafNodeLineNumbers in this CL)
      produces a tree, with each node representing a stack frame that is seen
      in one or more samples taken during profiling. These nodes refer to a
      particular function in a stack trace, but not to a particular line or
      callsite within that function.
      
      This CL adds a new more (called kCallerLineNumbers) which produces a
      different profile tree, where each stack trace seen during profiling,
      including the line number, has a unique path in the tree.
      
      The profile tree was previously keyed on CodeEntry*. Now it is keyed on
      the pair of CodeEntry* and line_number, meaning it has distinct nodes
      for those combinations which exist, and each distinct stack trace that
      was sampled is represented in the tree.
      
      For optimized code where we have inline frames, there are no line
      numbers for the inline frames in the stack trace, causing duplicate
      branches in the tree with kNoLineNumberInfo as the reported line number.
      This will be addressed in follow-ups.
      
      Bug: v8:7018
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I512e221508f5b50ec028306d212263b514a9fb24
      Reviewed-on: https://chromium-review.googlesource.com/1013493
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53298}
      ecae80cd
  33. 11 Apr, 2018 1 commit
  34. 20 Mar, 2018 2 commits
  35. 09 Mar, 2018 1 commit
  36. 07 Mar, 2018 1 commit
  37. 22 Feb, 2018 1 commit
  38. 20 Feb, 2018 1 commit
    • Ulan Degenbaev's avatar
      [heap-profiler] Merge embedder nodes and V8 wrapper nodes. · 252e8a1c
      Ulan Degenbaev authored
      Each DOM node has the corresponding V8 wrapper object. This leads to
      apparent duplication in the heap snapshot and may confuse the users.
      
      This patch allows the embedder to specify V8 wrapper for each embedder
      node. In the heap snapshot the wrapper node will be merged into the
      embedder node. The resulting node will have the same properties as
      the embedder node. If the wrapper node name has a tag, then the tag
      is also added to the merged node.
      
      Bug: chromium:811925
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I2492f5b28163a78aee707b9ced1b09ac4b203e3f
      Reviewed-on: https://chromium-review.googlesource.com/919482
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarAlexei Filippov <alph@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51394}
      252e8a1c