[v25.x backport] src: convert context_frame field in AsyncWrap to internal field#62357
[v25.x backport] src: convert context_frame field in AsyncWrap to internal field#62357aduh95 merged 0 commit intonodejs:v25.x-stagingfrom
Conversation
|
Finally I was able to reproduce the failed test locally by using clang (19.1.1) like in Github CI instead gcc (13.3.0). I'm not that a big expert on V8 internals/snapshots. @addaleax @joyeecheung any hints welcome how to find out why v25 shows these instability in snapshot creation. |
|
I found a bit more:
Anyhow, rebasing to tip of My best guess is that there is some sort of instability in snapshot generation which is just not visible on main as of now - and now also not on v25. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
Landed in 0e4af84 |
Using an internal field instead of a `v8::Global<>` removes an unnecessary memory leak footgun. This includes a test that demonstrates the issue, albeit using internal APIs. It's worth noting that if this PR is not accepted, we'd still be missing memory tracking for the `context_frame_` field, and we'd need to add it through our memory tracking API. PR-URL: #62103 Backport-PR-URL: #62357 Reviewed-By: Anna Henningsen <anna@addaleax.net>
Using an internal field instead of a `v8::Global<>` removes an unnecessary memory leak footgun. This includes a test that demonstrates the issue, albeit using internal APIs. It's worth noting that if this PR is not accepted, we'd still be missing memory tracking for the `context_frame_` field, and we'd need to add it through our memory tracking API. PR-URL: #62103 Backport-PR-URL: #62357 Reviewed-By: Anna Henningsen <anna@addaleax.net>
Using an internal field instead of a `v8::Global<>` removes an unnecessary memory leak footgun. This includes a test that demonstrates the issue, albeit using internal APIs. It's worth noting that if this PR is not accepted, we'd still be missing memory tracking for the `context_frame_` field, and we'd need to add it through our memory tracking API. PR-URL: #62103 Backport-PR-URL: #62357 Reviewed-By: Anna Henningsen <anna@addaleax.net>
Backport the second (7dd5ca8 / 6ad5f7c) commit of #62103 as it failed in 25.8.1 release. The other two commits were included in 25.8.1
Refs: #62103