Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: cherry-pick commits to be forward-compatible with V8 10.8 #44958

Closed
wants to merge 4 commits into from

Commits on Oct 11, 2022

  1. deps: V8: cherry-pick 8b8703953616

    Original commit message:
    
        [API] Remove second OnCriticalMemoryPressure
    
        Remove the deprecated OnCriticalMemoryPressure method with receives an
        informative parameter.
    
        R=mlippautz@chromium.org
    
        Bug: chromium:634547
        Change-Id: I932c3b5030291294dd340362f0b20d374e3067c0
        Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3780533
        Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
        Commit-Queue: Clemens Backes <clemensb@chromium.org>
        Cr-Commit-Position: refs/heads/main@{#83254}
    
    Refs: v8/v8@8b87039
    targos committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    842bd96 View commit details
    Browse the repository at this point in the history
  2. deps: V8: cherry-pick 3d59a3c2c164

    Original commit message:
    
        Add option to report discarded allocations in sampling heap profiler
    
        A couple of customers have asked about using devtools to get information
        about temporary allocations, with the goal of reducing GC time and/or
        peak memory usage. Currently, the sampling heap profiler reports only
        objects which are still alive at the end of the profiling session. In
        this change, I propose adding configuration options when starting the
        sampling heap profiler so that it can optionally include information
        about objects which were discarded by the GC before the end of the
        profiling session. A user could run the sampling heap profiler in
        several different modes depending on their goals:
    
        1. To find memory leaks or determine which functions contribute most to
           steady-state memory consumption, the current default mode is best.
        2. To find functions which cause large temporary memory spikes or large
           GC pauses, the user can request data about both live objects and
           those collected by major GC.
        3. To tune for minimal GC activity in latency-sensitive applications
           like real-time audio processing, the user can request data about
           every allocation, including objects collected by major or minor GC.
        4. I'm not sure why anybody would want data about objects collected by
           minor GC and not objects collected by major GC, but it's also a valid
           flags combination.
    
        Change-Id: If55d5965a1de04fed3ae640a02ca369723f64fdf
        Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3868522
        Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
        Reviewed-by: Camillo Bruni <cbruni@chromium.org>
        Reviewed-by: Simon Zünd <szuend@chromium.org>
        Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
        Cr-Commit-Position: refs/heads/main@{#83202}
    
    Refs: v8/v8@3d59a3c
    targos committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    82fb1af View commit details
    Browse the repository at this point in the history
  3. deps: V8: cherry-pick e7f0f26f5ef3

    Original commit message:
    
        Don't run sampling-heap-profiler-flags with stress-incremental-marking
    
        This test observes GC behavior and needs the garbage collector to work
        in a somewhat predictable way.
    
        Bug: v8:13286
        Change-Id: I24e6a4f33a644b5f1845cd34558da03fc196f7e5
        Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3898721
        Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
        Reviewed-by: Simon Zünd <szuend@chromium.org>
        Cr-Commit-Position: refs/heads/main@{#83218}
    
    Refs: v8/v8@e7f0f26
    targos committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    775476c View commit details
    Browse the repository at this point in the history
  4. deps: V8: cherry-pick c3dffe6e2bda

    Original commit message:
    
        [api] Expose parsed module source map urls
    
        Source map urls can be parsed from the magic comments. Expose them with
        public apis on the UnboundModuleScript, similar to the UnboundScript.
    
        Change-Id: Ia5dfdc8ff25f825c9fa7d241d0d79ba20028586b
        Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3917379
        Reviewed-by: Camillo Bruni <cbruni@chromium.org>
        Commit-Queue: Chengzhong Wu (legendecas) <legendecas@gmail.com>
        Cr-Commit-Position: refs/heads/main@{#83527}
    
    Refs: v8/v8@c3dffe6
    targos committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    ae1d02c View commit details
    Browse the repository at this point in the history