Please also consider this request here: https://bugs.chromium.org/p/v8/issues/detail?id=6433 I think the idea is that the external references are provided in a table that doesn't need to be copied over into V8 and can be referenced directly, when deserializing.
I could work on this once I return from leave in three weeks if you can wait that long. Cheers, Yang On Thu, Jun 15, 2017, 09:33 Bradley Farias <[email protected]> wrote: > Right now SnapshotCreator must declare up front *all* the external > references it may need when it is allocated. For some workflows, such as > snapshotting the state of a Node.js process this is problematic. The list > of external references can change since `.node` files can load in C++ code > that generates templates. I am willing to update `CreateBlob` to accept an > external_references argument but wanted to know any other concerns before > doing so. I don't see it being exposed publicly in any way after an Isolate > is created, but may be wrong. > > I also got wind that peria might want a format change for something around > this API according to @hashseed and have CC'd to figure out what change is > desired if/while I make a CL. > > -- > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
