[v8-users] access violation on Persistent.Reset()

Hi, I have an issue where we sometimes have Persistent handles that outlive the Isolate with which they are associated. When Reset() is called, it causes an access violation, seemingly because the Isolate no longer exists. Is there any way to prevent this (other than avoiding calling Reset() on

[v8-users] how to create a Persistent handle cache?

I would like to cache Persistent handles in such a way that I can retrieve the same Persistent instance given the identical JS object, i.e. imagine a function like so: Persistent GetPersistentForObject(Local obj) { // If we have already created a Persistent for obj, find and return it. //

Re: [v8-users] how to create a Persistent handle cache?

Thank you for the suggestion Ben! On Tuesday, November 10, 2020 at 5:14:35 AM UTC-5 Ben Noordhuis wrote: > On Tue, Nov 10, 2020 at 4:54 AM jres...@gmail.com > wrote: > > > > I would like to cache Persistent handles in such a way that I can > retrieve the same Persiste