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
The current GC strategy is to just clear all allocations at the end of each call, but we need to allow the JS ArrayBuffers to hold on to the memory they expose. This likely involves integration into the JS GC to ensure it can become a managed pointer in the engine.
The text was updated successfully, but these errors were encountered:
This is still a very important issue to resolve. We need to properly integrate the cabi_post calls so that they free non-rooted data, and retain the rooted data structures. In the case of rooted data structures, the pointer is the target of the free call to integrate into the JS GC (zero-copy strings and typed arrays).
The current GC strategy is to just clear all allocations at the end of each call, but we need to allow the JS ArrayBuffers to hold on to the memory they expose. This likely involves integration into the JS GC to ensure it can become a managed pointer in the engine.
The text was updated successfully, but these errors were encountered: