Thanks for emailing me! No, I haven’t been hacked :)
I signed up for a spam filtering service called BitBounce. To deliver your
email to my inbox, please click the link below. Thanks!
https://bitbounce.com/pay_bitbounce_fee/4119332566
BitBounce is a product by:
Turing Technology, Inc.
BitBoun
AFAIK that's correct. The polluted warmup context is thrown out, and a
second clean context (with the now-compiled code) is serialized into the
warmed up snapshot.
On Thu, Mar 1, 2018 at 5:31 PM, Johannes Rieken
wrote:
> Great! Thanks for the speedy reply. Looking at https://cs.chromium.org/
> c
Thanks for emailing me! No, I haven’t been hacked :)
I signed up for a spam filtering service called BitBounce. To deliver your
email to my inbox, please click the link below. Thanks!
https://bitbounce.com/pay_bitbounce_fee/332072661
BitBounce is a product by:
Turing Technology, Inc.
BitBounc
Great! Thanks for the speedy reply. Looking
at
https://cs.chromium.org/chromium/src/v8/test/cctest/test-serialize.cc?type=cs&q=CustomSnapshotDataBlobWithWarmup&l=1167
makes me think/hope that functions are being compiled but state isn't
changed (e.g. the assignment to `a` isn't persistent). I
On Thu, Mar 1, 2018 at 4:43 PM, Johannes Rieken
wrote:
>
> Hey,
>
> Can someone help me understand what the difference between a warm and cold
> snapshot is? I stumbled over `WarmUpSnapshotDataBlob` but I am not
> entirely sure how to make use of them via the mksnapshot-tools and what the
> seque
