Skip to content

V
V8
Switch branch/tag
  1. 16 Jan, 2014 1 commit
  3. 02 Jan, 2014 1 commit
  5. 20 Dec, 2013 1 commit
  7. 05 Dec, 2013 1 commit
  9. 27 Nov, 2013 2 commits
  11. 26 Nov, 2013 1 commit
  13. 22 Nov, 2013 3 commits
  15. 21 Nov, 2013 4 commits
  17. 20 Nov, 2013 1 commit
  19. 19 Nov, 2013 2 commits
  21. 14 Nov, 2013 1 commit
    • yurys@chromium.org's avatar
      This is the exact copy of r17365 which was reverted in r17488 due to memory... · c7b1b79e
      yurys@chromium.org authored 
      This is the exact copy of r17365 which was reverted in r17488 due to memory corruption. The root cause for the memory corruption - missing check for bump pointer limit before storing filler map must be addressed in r17626 where allocation hooks were removed from the generated code and left only in the runtime.

This is initial implementation of allocation profiler.

Whenever new object allocation is reported to the HeapProfiler and allocation tracking is on we will capture current stack trace, add it to the collection of the allocation traces (a tree) and attribute the allocated size to the top JS function on the stack.

Format of serialized heap snapshot is extended to include information about recorded allocation stack traces.

This patch is r17301 plus a fix for the test crash in debug mode. The test crashed because we were traversing stack trace when just allocated object wasn't completely configured, in particular the map pointer was incorrect. Invalid Map pointer broke heap iteration required to find Code object for a given pc during stack traversal. The solution is to insert free space filler in the newly allocated block just before collecting stack trace.

BUG=chromium:277984,v8:2949
R=bmeurer@chromium.org

Review URL: https://codereview.chromium.org/61893031

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17742 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c7b1b79e
  23. 07 Nov, 2013 1 commit
  25. 05 Nov, 2013 1 commit
  27. 24 Oct, 2013 1 commit
    • yurys@chromium.org's avatar
      Record allocation stack traces · a083601e
      yurys@chromium.org authored 
      This is initial implementation of allocation profiler.

Whenever new object allocation is reported to the HeapProfiler and allocation tracking is on we will capture current stack trace, add it to the collection of the allocation traces (a tree) and attribute the allocated size to the top JS function on the stack.

Format of serialized heap snapshot is extended to include information about recorded allocation stack traces.

This patch is r17301 plus a fix for the test crash in debug mode. The test crashed because we were traversing stack trace when just allocated object wasn't completely configured, in particular the map pointer was incorrect. Invalid Map pointer broke heap iteration required to find Code object for a given pc during stack traversal. The solution is to insert free space filler in the newly allocated block just before collecting stack trace.

BUG=chromium:277984,v8:2949
R=hpayer@chromium.org, loislo@chromium.org

Review URL: https://codereview.chromium.org/34733004

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17365 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a083601e
  29. 22 Oct, 2013 1 commit
  31. 21 Oct, 2013 2 commits
  33. 16 Oct, 2013 1 commit
  35. 15 Oct, 2013 2 commits
  37. 11 Oct, 2013 1 commit
  39. 04 Oct, 2013 2 commits
  41. 02 Oct, 2013 1 commit
  43. 30 Sep, 2013 1 commit
  45. 27 Sep, 2013 2 commits
  47. 26 Sep, 2013 2 commits
  49. 24 Sep, 2013 1 commit
  51. 23 Sep, 2013 1 commit
  53. 17 Sep, 2013 2 commits