You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Dart objects are holding on to external memory, e.g. when typed data objects are allocated with external memory for backing store, there is no way for the GC to know that running a GC could free much more memory that what the VM heap holds.
Dart could have an API like this or the number of external bytes could be aded to some other API where the finalization is registered, to avoid the need to two matching calls to increment and decrement the number of external bytes
The text was updated successfully, but these errors were encountered:
When Dart objects are holding on to external memory, e.g. when typed data objects are allocated with external memory for backing store, there is no way for the GC to know that running a GC could free much more memory that what the VM heap holds.
V8 has the API AdjustAmountOfExternalAllocatedMemory (https://code.google.com/p/v8/source/browse/branches/bleeding_edge/include/v8.h#3909) to indicate the amount of external memory kept alive by the V8 heap.
Dart could have an API like this or the number of external bytes could be aded to some other API where the finalization is registered, to avoid the need to two matching calls to increment and decrement the number of external bytes
The text was updated successfully, but these errors were encountered: