bytecodealliance / bytecodealliance/ComponentizeJS

Repeated calls to an instance start failing

Aberta
#80 12 comentários 1 reação 0 responsáveis Ver no GitHub
bug
Linguagem predominante
Rust
Estrelas
391
Forks
53
Merge médio
3d 5h
PRs com merge (30d)
1

Descrição

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)
```

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
javascript, rust, wasm
Domínio
tooling
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.