test-snapshot-* fail with "CheckGlobalAndEternalHandles failed"
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 50/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, node.js
- 领域
- build-system, testing
调研方向
Start by reviewing the linked CI run and the snapshot creation path shown in the stack trace, especially node::SnapshotBuilder::CreateSnapshot. Reproduce with V8 15.9.23 by running the affected test-snapshot-* tests, then trace why the global handle is not serialized. Done means the snapshot tests and the named inspect and benchmark tests complete without the fatal error.
由索引模型根据 Issue 内容生成。
描述
With V8 15.9.23, test-snapshot-*, test-inspect-address-in-use and test-benchmark-v8 crash while building a snapshot.
parallel/test-snapshot-basic:
#
# Fatal error
# CheckGlobalAndEternalHandles failed
#
#
#
#FailureMessage Object: 0x7fff1154efe0
----- Native stack trace -----
1: 0x55b1041bee12 [/home/runner/work/node-v8/node-v8/node/out/Release/node]
2: 0x55b106cf338f V8_Fatal(char const*, ...) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
3: 0x55b104be9390 [/home/runner/work/node-v8/node-v8/node/out/Release/node]
4: 0x55b10420f8b9 node::SnapshotBuilder::CreateSnapshot(node::SnapshotData*, node::CommonEnvironmentSetup*) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
5: 0x55b10420f280 node::BuildSnapshotWithoutCodeCache(node::SnapshotData*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, std::optional<std::basic_string_view<char, std::char_traits<char> > >, node::SnapshotConfig const&) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
6: 0x55b10420ffa7 node::SnapshotBuilder::Generate(node::SnapshotData*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, std::optional<std::basic_string_view<char, std::char_traits<char> > >, node::SnapshotConfig const&) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
7: 0x55b1040a5d4e node::GenerateAndWriteSnapshotData(node::SnapshotData const**, node::InitializationResultImpl const*) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
8: 0x55b1040a6875 node::Start(int, char**) [/home/runner/work/node-v8/node-v8/node/out/Release/node]
9: 0x7f20b242a1ca [/lib/x86_64-linux-gnu/libc.so.6]
10: 0x7f20b242a28b __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
11: 0x55b103f84dc5 _start [/home/runner/work/node-v8/node-v8/node/out/Release/node]
[process 178895]: --- stdout ---
(Global handles) handle not serialized: 0xf4c5113dcd1: [EphemeronHashTable] in OldSpace
- FixedArray length: 67
- elements: 1
- deleted: 1
- capacity: 32
- elements: {
7: 0x2dd89cccdd29 <Script> -> 0x2dd89cccf031 <Other heap object (WEAK_ARRAY_LIST_TYPE)>
}
CI run: https://github.com/nodejs/node-v8/actions/runs/40665664178
- 主要语言
- Shell
- 星标
- 468
- 派生
- 75
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nodejs/node-v8 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 45/100
-
难度 3/5 1-2 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 30/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
heroku/heroku-buildpack-php#1024 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
openSUSE/rpm-config-SUSE#98 ·
-
package-update
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复