New issue
Advanced search Search tips

Issue 756039 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Unify memory management in V8 and Blink

Project Member Reported by bbudge@google.com, Aug 16 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. N/A
2. 
3. 

What is the expected behavior?

What went wrong?
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.

Did this work before? N/A 

Chrome version: 60.0.3112.90  Channel: n/a
OS Version: OS X 10.12.6
Flash Version:
 

Comment 1 by bbudge@chromium.org, Aug 16 2017

Status: WontFix (was: Unconfirmed)

Sign in to add a comment