René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Segfaults with `[await] using` within node core","articleBody":"`js_explicit_resource_management` is still a flagged feature in V8. We cannot depend on it in core.\n\nEncountering `[await] using` in core will segfault if running in an environment without `js_shipping` features.\n\n```console\n\u003e out/Release/node --no-js-explicit-resource-management --eval 'diagnostics_channel.tracingChannel(\"foo\").traceSync(() =\u003e {})'\n[1]    160425 segmentation fault (core dumped)  out/Release/node --no-js-explicit-resource-management --eval\n```\n\n(This only applies to core, not the test suite.)\n\n- We should convert cases added by #61680 from\n  ```js\n  {\n    using _ = blah;\n    ...\n  }\n  ```\n  to\n  ```js\n  {\n    const _ = blah;\n    try {\n      ...\n    } finally {\n      _[Symbol.dispose]();\n    }\n  }\n  ```\n  (cc @Qard)\n- I'll add an eslint rule to cover it.\n- Should we be doing a GHA CI run with `--no-js-shipping` in the global test options?","author":{"url":"https://github.com/Renegade334","@type":"Person","name":"Renegade334"},"datePublished":"2026-07-01T13:39:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/64230/node/issues/64230"}