Skip to content

V
V8
Switch branch/tag
  1. 23 Jul, 2015 1 commit
  3. 06 Jul, 2015 2 commits
  5. 02 Jul, 2015 2 commits
  7. 26 Jun, 2015 1 commit
  9. 24 Jun, 2015 1 commit
  11. 18 Jun, 2015 1 commit
  13. 16 Jun, 2015 1 commit
  15. 29 May, 2015 1 commit
  17. 28 May, 2015 2 commits
  19. 27 May, 2015 1 commit
    • ulan's avatar
      New algorithm for selecting evacuation candidates · 5e87a099
      ulan authored 
      This lifts the sqrt(n) limit on number of evacuation candidates,
replaces O(n * sqrt(n)) algorithm with O(n*log(n)) algorithm, and
removes hard-coded constants.

Evacuation candidates are selected as follows:

1) Sort pages from the most free to the least free.

2) Select the first m pages as evacuation candidates such that m is as
large as possible under the two conditions:

- The total size of live objects in the first m pages does not exceed
the given limit. This is based on the assumption that the evacuation cost is
proportional to the total size of moved objects.

- The fragmentation of the (m+1)-th page does not exceed the given
limit.

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

Cr-Commit-Position: refs/heads/master@{#28651}
      5e87a099
  21. 22 May, 2015 1 commit
  23. 21 May, 2015 1 commit
  25. 15 May, 2015 2 commits
  27. 12 May, 2015 1 commit
  29. 06 May, 2015 2 commits
  31. 04 May, 2015 1 commit
  33. 20 Apr, 2015 1 commit
  35. 17 Apr, 2015 1 commit
    • ssid's avatar
      Adding V8 api to get memory statistics of spaces in V8::Heap. · 281d30d7
      ssid authored 
      This is first step towards adding V8 heap statistics to the memory
tracing infrastructure. For being able to get useful memory number into
the memory dump, v8 needs to provide an external api needs to obtain
more information about the heap. So, this Cl extends the api to give
information about the memory allocated and used in the spaces.

BUG=466141, 476013
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#27919}
      281d30d7
  37. 16 Apr, 2015 2 commits
  39. 10 Apr, 2015 1 commit
  41. 09 Apr, 2015 3 commits
  43. 07 Apr, 2015 1 commit
  45. 27 Mar, 2015 2 commits
  47. 25 Mar, 2015 1 commit
    • ulan's avatar
      Reland "Filter invalid slots out from the SlotsBuffer after marking." · f86aadd1
      ulan authored 
      > There are two reasons that could cause invalid slots appearance in SlotsBuffer:
> 1) If GC trims "tail" of an array for which it has already recorded a slots and then migrate another object to the "tail".
> 2) Tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).

> This CL also adds useful machinery that helps triggering incremental write barriers.

> BUG=chromium:454297
> LOG=Y

NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#27433}
      f86aadd1
  49. 24 Mar, 2015 3 commits
    • machenbach's avatar
      Revert of Filter invalid slots out from the SlotsBuffer after marking.... · 4629f802
      machenbach authored 
      Revert of Filter invalid slots out from the SlotsBuffer after marking. (patchset #6 id:220001 of https://codereview.chromium.org/1010363005/)

Reason for revert:
Need to revert in order to revert https://codereview.chromium.org/1029323003/

Original issue's description:
> Filter invalid slots out from the SlotsBuffer after marking.
>
> There are two reasons that could cause invalid slots appearance in SlotsBuffer:
> 1) If GC trims "tail" of an array for which it has already recorded a slots and then migrate another object to the "tail".
> 2) Tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).
>
> This CL also adds useful machinery that helps triggering incremental write barriers.
>
> BUG=chromium:454297
> LOG=Y
>
> Committed: https://crrev.com/5c47c1c0d3e4a488f190c16a64ee02f5a14e6561
> Cr-Commit-Position: refs/heads/master@{#27423}

TBR=hpayer@chromium.org,erik.corry@gmail.com,ishell@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:454297

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

Cr-Commit-Position: refs/heads/master@{#27426}
      4629f802
    • ishell's avatar
      Filter invalid slots out from the SlotsBuffer after marking. · 5c47c1c0
      ishell authored 
      There are two reasons that could cause invalid slots appearance in SlotsBuffer:
1) If GC trims "tail" of an array for which it has already recorded a slots and then migrate another object to the "tail".
2) Tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).

This CL also adds useful machinery that helps triggering incremental write barriers.

BUG=chromium:454297
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#27423}
      5c47c1c0
    • erikcorry's avatar
      Fix OOM bug 3976. · 4c806802
      erikcorry authored 
      Also introduce --trace-fragmentation-verbose, and fix --always-compact.

R=ulan@chromium.org
BUG=v8:3976
LOG=y

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

Cr-Commit-Position: refs/heads/master@{#27414}
      4c806802
  51. 19 Mar, 2015 1 commit
  53. 18 Mar, 2015 2 commits
  55. 16 Mar, 2015 1 commit
    • ishell's avatar
      Revert of Reland of Remove slots that point to unboxed doubles from the... · 52cb51fb
      ishell authored 
      Revert of Reland of Remove slots that point to unboxed doubles from the StoreBuffer/SlotsBuffer. (patchset #3 id:40001 of https://codereview.chromium.org/988363002/)

Reason for revert:
Increased rate of Chrome crashes. Requires further investigation.

Original issue's description:
> Reland of Remove slots that point to unboxed doubles from the StoreBuffer/SlotsBuffer.
>
> The problem is that tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).
> This CL also adds useful machinery that helps triggering incremental write barriers.
>
> BUG=chromium:454297, chromium:465273
> LOG=Y
>
> Committed: https://crrev.com/6d0677d845c47ab9fa297de61d0e3d8e5480a02a
> Cr-Commit-Position: refs/heads/master@{#27141}

TBR=hpayer@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:454297, chromium:465273

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

Cr-Commit-Position: refs/heads/master@{#27207}
      52cb51fb