Skip to content

V
V8
Switch branch/tag
  1. 09 Jan, 2017 1 commit
  3. 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
  5. 02 Sep, 2016 1 commit
  7. 25 Jul, 2016 1 commit
  9. 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
  13. 09 Dec, 2015 1 commit
  15. 26 Nov, 2015 1 commit
  17. 23 Nov, 2015 1 commit
  19. 18 Nov, 2015 1 commit
  21. 13 Jul, 2015 1 commit
  23. 29 Apr, 2015 1 commit
  25. 17 Apr, 2015 1 commit
  27. 27 Mar, 2015 1 commit
  29. 30 Jan, 2015 3 commits
  31. 19 Jan, 2015 1 commit
  33. 08 Oct, 2014 1 commit
  35. 12 Aug, 2014 1 commit
  37. 30 Jun, 2014 1 commit
  39. 24 Jun, 2014 1 commit
  41. 03 Jun, 2014 1 commit
  43. 22 Nov, 2013 1 commit
  45. 20 Sep, 2013 1 commit
  47. 19 Sep, 2013 3 commits
  49. 02 Sep, 2013 1 commit
  51. 27 Aug, 2013 1 commit
  53. 05 Jul, 2013 1 commit
  55. 28 Jun, 2013 1 commit
  57. 28 May, 2013 2 commits
  59. 13 May, 2013 1 commit
  61. 08 May, 2013 1 commit
  63. 07 May, 2013 2 commits
  65. 02 May, 2013 1 commit
  67. 24 Apr, 2013 1 commit