bytecodealliance / bytecodealliance/ComponentizeJS

Repeated calls to an instance start failing

未關閉
#80 12 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視
bug
主要語言
Rust
星號
391
分支
53
平均合併
3 天 5 小時
30 天內合併 PR
1

描述

We're testing long-lived component instances created with ComponentizeJS. After some number of calls to an instance we start getting failures, wasm traps such as unreachable or uninitialized value. The number of calls before a failure seems to vary based on the functions called and the data returned, but it consistently fails given the same pattern of calls.

I've created a test case using the ComponentizeJS testing here: https://github.com/bytecodealliance/ComponentizeJS/compare/main...pvlugter:ComponentizeJS:repeated-calls

Which fails after 1805 calls with:

```
RuntimeError: failed on attempt [1806]: null function or function signature mismatch
at js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (wasm://wasm/029a3d3a:wasm-function[337]:0x193642)
at js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle, js::CallReason) (wasm://wasm/029a3d3a:wasm-function[6458]:0x58cc39)
at JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) (wasm://wasm/029a3d3a:wasm-function[1448]:0x31b2b4)
at call(unsigned int, void*) (wasm://wasm/029a3d3a:wasm-function[500]:0x1e76dc)
at exports#hello (wasm://wasm/029a3d3a:wasm-function[14509]:0x67e160)
at Object.hello (file:///.../ComponentizeJS/test/output/repeated-calls/repeated-calls.js:1430:40)
at Module.test (file:///.../ComponentizeJS/test/cases/repeated-calls/test.js:6:36)
at Context. (file:///.../ComponentizeJS/test/test.js:138:18)
```

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

Start with test/cases/repeated-calls/test.js and the linked ComponentizeJS repeated-calls test case, then inspect the generated test/output/repeated-calls/repeated-calls.js around the reported call path. Run the case to reproduce the failure after repeated instance calls. Done means the same call pattern completes without the reported wasm trap.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript, rust, wasm
領域
tooling
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。