bytecodealliance / bytecodealliance/ComponentizeJS
Repeated calls to an instance start failing
- Ngôn ngữ chính
- Rust
- Star
- 391
- Fork
- 53
- Merge trung bình
- 3 ngày 5 giờ
- Pull request đã merge (30 ngày)
- 1
Mô tả
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)
```
Hướng dẫn đóng góp
Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này
Hướng nghiên cứu
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.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- javascript, rust, wasm
- Lĩnh vực
- tooling
- Loại issue
- Lỗi
- Độ khó
- 4/5
- Thời gian dự kiến
- 3-5 ngày
- Mức độ hoạt động
- Đình trệ
- Độ rõ ràng
- Khá rõ ràng
- Mức phù hợp với người mới
- 35/100