René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Crash on node api add-on finalization","articleBody":"* **Version**: v10.23.2, v12.20.1, v14.15.4, v15.8.0 (all latest lts and current version)\r\n* **Platform**: all\r\n* **Subsystem**: node-api\r\n\r\n### What steps will reproduce the bug?\r\n\r\nRepo to re-produce: https://github.com/legendecas/repro-napi-v8impl-refbase-double-free\r\n\r\n```\r\n$ make\r\nv14.15.4\r\nforce gc\r\nfish: 'node --expose_gc index.js' terminated by signal SIGSEGV (Address boundary error)\r\n```\r\n\r\n### How often does it reproduce? Is there a required condition?\r\n\r\nAlways.\r\n\r\n### What is the expected behavior?\r\n\r\nNo segment faults.\r\n\r\n### What do you see instead?\r\n\r\nSegment faults on double free of `v8impl::\u003canonymous\u003e::RefBase`. The `RefBase`s were deleted once one module's napi_env was going to destroy, and the installed weak `v8impl::Persistent`s of `v8impl::\u003canonymous\u003eReference` was not destroyed and these `RefBase` will be deleted again on finalization callbacks.\r\n","author":{"url":"https://github.com/legendecas","@type":"Person","name":"legendecas"},"datePublished":"2021-02-05T08:40:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":20},"url":"https://github.com/37236/node/issues/37236"}