V8 and Chromium both request memory from the OS using different mechanisms. In V8, platform implementations and various other calls to malloc / free, new / delete may cause system memory to be allocated. In Blink, PartitionAllocator does this using the functions in base/allocator/partition_allocator/page_allocator.
We should change V8 to use embedder provided functions to manage memory, and Chromium to support V8's needs.
V8 and Chromium both request memory from the OS using different mechanisms. In V8, platform implementations and various other calls to malloc / free, new / delete may cause system memory to be allocated. In Blink, PartitionAllocator does this using the functions in base/allocator/partition_allocator/page_allocator.
We should change V8 to use embedder provided functions to manage memory, and Chromium to support V8's needs.
Design Doc:
https://docs.google.com/document/d/1PiUg9Bzlhhv8eVLYhfEkK9LKytFunRX_y6u_6ju8yok
Comment 1 by bugdroid1@chromium.org
, Sep 1 2017