On Tuesday, 27 February 2018 19:21:03 UTC-5, Ben Noordhuis wrote: > IIRC, it's a two-pass system: first pass should reset the persistent > handle, second pass is the real finalizer. Preempting the question of > why it works that way: I don't know. :-) >
Thanks for the insights. I think I see what you are saying, but even if I set up the second pass callback, both internal fields within the second callback are still `NULL`. How can I set up the weak callback to receive internal fields of the object instance that is being destroyed? I also noticed that the second pass callback is called much less frequent than the first callback and if the actual clean-up is done in the second callback, allocations would pile up at a higher rate. From the code it appears that the second pass callbacks are done only if `synchronous_second_pass` is set. Can you elaborate how second pass callbacks are scheduled? -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
