1. 19 Sep, 2018 1 commit
  2. 17 Aug, 2018 1 commit
  3. 25 Jul, 2018 3 commits
  4. 23 Jul, 2018 1 commit
  5. 04 Jul, 2018 1 commit
  6. 29 Jun, 2018 2 commits
  7. 27 Jun, 2018 1 commit
  8. 26 Jun, 2018 4 commits
  9. 21 Jun, 2018 1 commit
    • Peter Marshall's avatar
      [gc] Attach page to LocalArrayBufferTracker rather than space · 11926e6e
      Peter Marshall authored
      Each local ABT is logically for one page. We passed the space in to the
      constructor, but this is wrong because the space a page is in can
      change, e.g. for compaction pages.
      
      Instead, pass the page to the local ABT constructor and always get the
      space from this. To do this we need to push the AllocateLocalTracker()
      helper and friends down to Page, rather than its superclass MemoryChunk.
      
      Unfortunately, we need to keep ReleaseLocalTracker() on MemoryChunk even
      though only Pages can have local trackers, because we can't do virtual
      dispatch on MemoryChunk::ReleaseAllocatedMemory() which would allow us
      to clean up the tracker memory nicely for pages only.
      
      We also have to make sure we update external bytes accounting properly
      when swapping spaces, as in SemiSpace::Swap().
      
      Change-Id: Iff02e41dd12a6b04a57fcc32f9e2b4f049fcbc24
      Reviewed-on: https://chromium-review.googlesource.com/1107635
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53930}
      11926e6e
  10. 15 May, 2018 1 commit
    • Wez's avatar
      [heap] Replace retained_size() with ExternalBackingStoreBytes(). · aca33312
      Wez authored
      ArrayBuffer memory allocated off-heap was previously tracked by a test-
      only retained_size() field on each LocalArrayBufferTracker.
      
      Changes in off-heap ArrayBuffer memory usage are now reported to the
      Space with which the ArrayBuffer is associated, so that the value is
      cheaply available to include in e.g. GC limit calculations, via a new
      getter, ExternalBackingStoreBytes().
      
      Changes to external ArrayBuffer backing-store allocations are tracked in
      an AtomicNumber associated with each Space, to allow for ArrayBuffers
      being concurrently moved or freed from multiple Pages in the same Space
      during sweeps & compactions.
      
      Bug: chromium:837583
      Change-Id: I8b1b6addd5cd05533d8da55ca813e134bc36e181
      Reviewed-on: https://chromium-review.googlesource.com/1052347
      Commit-Queue: Wez <wez@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53192}
      aca33312
  11. 04 Oct, 2017 1 commit
  12. 11 Aug, 2017 1 commit
  13. 02 Aug, 2017 1 commit
  14. 13 Jun, 2017 1 commit
  15. 12 Jun, 2017 1 commit
  16. 31 May, 2017 1 commit
  17. 29 May, 2017 2 commits
  18. 27 Apr, 2017 3 commits
  19. 09 Jan, 2017 1 commit
  20. 03 Jan, 2017 1 commit
  21. 18 Nov, 2016 1 commit
  22. 03 Nov, 2016 1 commit
  23. 07 Sep, 2016 1 commit
  24. 01 Sep, 2016 1 commit
  25. 19 Aug, 2016 1 commit
  26. 18 Aug, 2016 1 commit
  27. 25 Jul, 2016 1 commit
    • bjaideep's avatar
      [Heap] Fix ArrayBuffer_SemiSpaceCopyMultipleTasks to respect PPC page size · b1683f05
      bjaideep authored
      The testcase allocates JSArraybuffer on 2 separate pages which should be
      on the New space. In the testcase semi space size is set to 2MB.
      Since page size on PPC is 4MB the semi new space size defaults to 4MB.
      Therefore when allocating 2nd buffer, scavenge GC kicks in as from-space is
      filled up and copies 1st buffer to to-space. Now, the 2nd buffer also gets
      allocated on the same to-space, therefore both buffer end up being on the
      same page. This fix should allocate enough semi new space to contain 2
      pages (for all platform).
      The testcase was added as part of https://codereview.chromium.org/2036643002
      
      R=mlippautz@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com
      
      BUG=
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2167853002
      Cr-Commit-Position: refs/heads/master@{#38028}
      b1683f05
  28. 07 Jun, 2016 1 commit
    • mlippautz's avatar
      Track based on JSArrayBuffer addresses on pages instead of the attached · 839f3fd4
      mlippautz authored
      backing store.
      
      Details of tracking:
      - Scavenge: New space pages are processes in bulk on the main thread
      - MC: Unswept pages are processed in bulk in parallel. All other pages
        are processed by the sweeper concurrently.
      
      BUG=chromium:611688
      LOG=N
      TEST=cctest/test-array-buffer-tracker/*
      CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg,v8_linux_gc_stress_dbg,v8_mac_gc_stress_dbg,v8_linux64_tsan_rel,v8_mac64_asan_rel
      
      Review-Url: https://codereview.chromium.org/2036643002
      Cr-Commit-Position: refs/heads/master@{#36798}
      839f3fd4
  29. 02 Jun, 2016 1 commit
  30. 01 Jun, 2016 1 commit
    • mlippautz's avatar
      Track based on JSArrayBuffer addresses on pages instead of the attached · 279e274e
      mlippautz authored
      backing store.
      
      Details of tracking:
      - Scavenge: New space pages are processes in bulk on the main thread
      - MC: Unswept pages are processed in bulk in parallel. All other pages
        are processed by the sweeper concurrently.
      
      BUG=chromium:611688
      LOG=N
      TEST=cctest/test-array-buffer-tracker/*
      CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg,v8_linux_gc_stress_dbg,v8_mac_gc_stress_dbg,v8_linux64_tsan_rel,v8_mac64_asan_rel
      
      Review-Url: https://codereview.chromium.org/2026633003
      Cr-Commit-Position: refs/heads/master@{#36653}
      279e274e
  31. 31 May, 2016 1 commit