Skip to content

V
V8
Switch branch/tag
  1. 13 Apr, 2015 1 commit
  3. 27 Jan, 2015 3 commits
  5. 04 Aug, 2014 1 commit
  7. 30 Jun, 2014 1 commit
  9. 20 Jun, 2014 1 commit
  11. 03 Jun, 2014 1 commit
  13. 29 Apr, 2014 1 commit
  15. 16 Apr, 2014 3 commits
  17. 15 Apr, 2014 1 commit
  19. 07 Mar, 2014 3 commits
  21. 18 Feb, 2014 1 commit
  23. 06 Feb, 2014 1 commit
  25. 18 Dec, 2013 1 commit
  27. 29 Nov, 2013 1 commit
    • yurys@chromium.org's avatar
      Do not put allocated block into HeapObjectsMap · 55674264
      yurys@chromium.org authored 
      Heap allocation reported to AllocationTracker may be later divided into several objects so it is incorrect to put the block as a new HeapObject into the map. We will match allocated block with actual HeapObjects later when iterating Heap (will be addressed in another patch). Since the objects are not assigned an id immediately after creation we need to call FindOrAddEntry when finding id for SharedFunctionInfo during stack crawling.

Removed hooks for tracking creation of AllocationMemento. AllocationMemento is not a HeapObject and should be considered as implementation overhead.

Renamed NewObjectEvent to AllocationEvent which is more precise in case of folded allocations and when a part of the new block becomes AllocationMemento.

BUG=None
LOG=N
R=loislo@chromium.org, mstarzinger@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18151 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      55674264
  29. 22 Nov, 2013 1 commit
  31. 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
  33. 05 Nov, 2013 1 commit
  35. 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
  37. 22 Oct, 2013 1 commit
  39. 21 Oct, 2013 1 commit
    • yurys@chromium.org's avatar
      Record allocation stack traces · 66bb9d15
      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.

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

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17301 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      66bb9d15