1. 21 Sep, 2017 1 commit
  2. 18 Sep, 2017 1 commit
    • Juliana Franco's avatar
      Deoptimization and multithreading. · 596d55ad
      Juliana Franco authored
      When using Lockers and Unlockers it is possible to create a
      scenario where multiple threads point to the same optimized
      code object. When that happens, if one of the threads triggers
      deoptimization, then the stack replacement needs to happen in
      the stacks of all threads.
      With this CL, the deoptimizer visits all threads to do so.
      The CL also adds three tests where V8 used to crash due to this
      issue.
      
      Bug: v8:6563
      Change-Id: I74e9af472d4833aa8d13e579df45133791f6a503
      Reviewed-on: https://chromium-review.googlesource.com/670783Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Juliana Patricia Vicente Franco <jupvfranco@google.com>
      Cr-Commit-Position: refs/heads/master@{#48060}
      596d55ad
  3. 15 Sep, 2017 2 commits
  4. 29 Aug, 2017 1 commit
  5. 28 Aug, 2017 1 commit
  6. 09 Jan, 2017 1 commit
  7. 08 Dec, 2016 1 commit
    • yangguo's avatar
      [serializer] include global proxy in additional context snapshots. · 98b563eb
      yangguo authored
      Aside from the default snapshot, there is no need for additional context
      snapshots to have the ability to replace the global proxy and global object
      after deserialization. Changes include:
       - Changes to the API to better distinguish default context snapshot from
         additional context snapshots.
       - Disallow global handles when creating snapshots.
       - Allow extensions when creating snapshots.
      
      This solves the issue of not being able to having accessors and interceptors on
      the global object of contexts to be serialized.
      
      R=jochen@chromium.org, peria@chromium.org
      BUG=chromium:617892
      
      Review-Url: https://codereview.chromium.org/2557743003
      Cr-Commit-Position: refs/heads/master@{#41588}
      98b563eb
  8. 02 Sep, 2016 1 commit
  9. 25 Jul, 2016 1 commit
  10. 15 Mar, 2016 1 commit
  11. 16 Dec, 2015 1 commit
    • akodat's avatar
      Add Isolate::DiscardThreadSpecificMetadata method to embedder API. · aeb8073c
      akodat authored
      If many threads use the same Isolate (or many Isolates) and then
      terminate, their PerIsolateThreadData objects are never cleaned
      up, resulting in a slow memory leak and, worse, the
      PerIsolateThreadData chain getting larger and larger, adversely
      affecting performance.
      
      In this situation, embedders will now be encouraged to apply
      DiscardThreadSpecificMetadata against any Isolate a thread is
      done with, especially if the thread is about to terminate.
      
      Note that it is harmless to run DiscardThreadSpecificMetadata
      against an Isolate for which a thread has no thread data and
      per-Isolate thread data can be reestablished if a thread starts
      using an Isolate again after running DiscardThreadSpecificMetadata
      against it.
      
      It is, however, an embedder error to run
      DiscardThreadSpecificMetadata against an Isolate in thread with a
      Locker for the Isolate in the stack or against an Entered Isolate.
      
      This change cannot cause any change in behavior in existing apps
      as the only added coded can only be reached via the new
      DiscardThreadSpecificMetadata method.
      
      R=Jakob, jochen
      BUG=
      
      Review URL: https://codereview.chromium.org/1522703002
      
      Cr-Commit-Position: refs/heads/master@{#32909}
      aeb8073c
  12. 09 Dec, 2015 1 commit
  13. 26 Nov, 2015 1 commit
  14. 23 Nov, 2015 1 commit
  15. 18 Nov, 2015 1 commit
  16. 13 Jul, 2015 1 commit
  17. 29 Apr, 2015 1 commit
  18. 17 Apr, 2015 1 commit
  19. 27 Mar, 2015 1 commit
  20. 30 Jan, 2015 3 commits
  21. 19 Jan, 2015 1 commit
  22. 08 Oct, 2014 1 commit
  23. 12 Aug, 2014 1 commit
  24. 30 Jun, 2014 1 commit
  25. 24 Jun, 2014 1 commit
  26. 03 Jun, 2014 1 commit
  27. 22 Nov, 2013 1 commit
  28. 20 Sep, 2013 1 commit
  29. 19 Sep, 2013 3 commits
  30. 02 Sep, 2013 1 commit
  31. 27 Aug, 2013 1 commit
  32. 05 Jul, 2013 1 commit
  33. 28 Jun, 2013 1 commit
  34. 28 May, 2013 2 commits