1. 11 Jun, 2019 26 commits
  2. 10 Jun, 2019 4 commits
  3. 09 Jun, 2019 2 commits
  4. 08 Jun, 2019 5 commits
  5. 07 Jun, 2019 3 commits
    • Johannes Henkel's avatar
      [DevTools] Roll inspector_protocol. · 06663094
      Johannes Henkel authored
      New rev: 91eb1c8784ab3d88ca1e327ffa727d922dd2ce70
      
      Change-Id: I0be17a324ff64b2ee6c2657e3c2cea5d09f6c494
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1649227
      Auto-Submit: Johannes Henkel <johannes@chromium.org>
      Reviewed-by: 's avatarAlexei Filippov <alph@chromium.org>
      Commit-Queue: Alexei Filippov <alph@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62060}
      06663094
    • Irina Yatsenko's avatar
      Add Crash Keys support · 02103b27
      Irina Yatsenko authored
      This adds crash keys containing the isolate address and addresses of
      the read_only, map, and code spaces to crash report minidumps.
      When not compiling V8 with Chrome, a noop implementation is used.
      
      Bug: v8:9323
      Change-Id: I8523630e7a4ff792855163c06bf76dab35b1b9e5
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1641326Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Irina Yatsenko <irinayat@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#62059}
      02103b27
    • Darius Mercadier's avatar
      Makes sure FreeListCategories never contain empty elements · 303ca9ac
      Darius Mercadier authored
      The linked lists of FreeLists could contain empty elements
      (FreeListCategories whose `top()` is null). The code is carefuly
      written so that this case won't break anything (probably just slow
      things a little bit).  When `FreeList::FindNodeIn` (the fast path of
      `FreeList::Allocate`) found such an empty `FreeListCategory`, it
      removed it by calling `FreeList::RemoveCategory`, and looked in the
      next `FreeListCategory` of the same size. However, on the slow path of
      `FreeList::Allocate`, the functions that iterates the
      `FreeListCategory` are `FreeList::TryFindNodeIn` and
      `FreeListCategory::PickNodeFromList`, none of which removed empty
      elements. Therefore, it could happen that a `FreeListCategory` "real"
      first element could be used, but was never considered due to the top of
      the linked list being empty. The behavior for the slow path should be
      the same as for the fast path on that regard.
      
      The problem was actually deeper than that: FreeListCategories were not
      always in a consistent state, since they could have empty members. The
      removal of those empty elements should be done as soon as they are
      created, ie when allocating the last element.
      
      This CL ensures that empty FreeListCategories are removed as soon as
      they become empty.
      
      Bug: v8:9329
      Change-Id: Idda8096dc5978745894854a0405da59f7e8691a6
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1648476
      Commit-Queue: Darius Mercadier <dmercadier@google.com>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62058}
      303ca9ac