Skip to content

V
V8
Switch branch/tag
  1. 04 Apr, 2016 1 commit
  3. 22 Feb, 2016 1 commit
  5. 12 Feb, 2016 1 commit
  7. 25 Nov, 2015 1 commit
    • jochen's avatar
      Double the API call rate threshold for the memory reducer to kick in · 9ec240d0
      jochen authored 
      Moving Blink from hidden values to private symbols almost doubled the
rate of API calls, as the private symbols API increases the call-depth
scope while the hidden values one didn't.

I manually checked that this fixes the regression on the long running
gmail benchmark but doesn't add new memory reducer GCs on the infinite
scrolling benchmark

BUG=chromium:561325
R=ulan@chromium.org
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#32279}
      9ec240d0
  9. 06 Nov, 2015 1 commit
  11. 29 Oct, 2015 1 commit
  13. 27 Oct, 2015 1 commit
  15. 22 Oct, 2015 1 commit
  17. 05 Oct, 2015 1 commit
  19. 02 Oct, 2015 1 commit
  21. 30 Sep, 2015 1 commit
  23. 29 Sep, 2015 1 commit
  25. 03 Sep, 2015 1 commit
  27. 01 Sep, 2015 1 commit
  29. 31 Aug, 2015 2 commits
    • hablich's avatar
      Revert of [heap] More flag cleanup. (patchset #8 id:140001 of... · 6eb83769
      hablich authored 
      Revert of [heap] More flag cleanup. (patchset #8 id:140001 of https://codereview.chromium.org/1314863003/ )

Reason for revert:
Breaks http://build.chromium.org/p/client.v8/builders/V8%20Arm%20-%20debug%20-%202/builds/2372

Original issue's description:
> [heap] GC flag cleanup/restructuring.
>
> * GC's flags are now proper flags and not int.
> * Callback flags are not threaded through but only set once like gc flags
> * Callers of methods that trigger GCs need to pass a reason when not using
>   the default parameters.
>
> Furthermore, each GC invocation can be passed the GC and GCCallback flags. We
> usually override the currently set flags upon finishing a GC cylce, but are able
> to restore the previously set if desired. This is useful for explicitely
> triggered scavenges or external requests that interrupt the current behaviour.
>
> BUG=
>
> Committed: https://crrev.com/f4f3b431b9ce0778d926acf03c0d36dae5c0cba4
> Cr-Commit-Position: refs/heads/master@{#30457}

TBR=hpayer@chromium.org,yangguo@chromium.org,mlippautz@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

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

Cr-Commit-Position: refs/heads/master@{#30463}
      6eb83769
    • mlippautz's avatar
      [heap] GC flag cleanup/restructuring. · f4f3b431
      mlippautz authored 
      * GC's flags are now proper flags and not int.
* Callback flags are not threaded through but only set once like gc flags
* Callers of methods that trigger GCs need to pass a reason when not using
  the default parameters.

Furthermore, each GC invocation can be passed the GC and GCCallback flags. We
usually override the currently set flags upon finishing a GC cylce, but are able
to restore the previously set if desired. This is useful for explicitely
triggered scavenges or external requests that interrupt the current behaviour.

BUG=

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

Cr-Commit-Position: refs/heads/master@{#30457}
      f4f3b431
  31. 24 Aug, 2015 1 commit
  33. 20 Aug, 2015 2 commits
  35. 07 Aug, 2015 2 commits
  37. 04 Aug, 2015 1 commit
  39. 03 Aug, 2015 1 commit
  41. 31 Jul, 2015 1 commit
  43. 20 Jul, 2015 1 commit
  45. 13 Jul, 2015 1 commit
  47. 10 Jul, 2015 1 commit
  49. 07 Jul, 2015 2 commits
  51. 05 Jul, 2015 1 commit
  53. 02 Jul, 2015 1 commit