InsightSoftwareConsortium / InsightSoftwareConsortium/ITK-Wasm
mean-squares-versor-registration example backtrace on WASI exit
- Dominant language
- Python
- Stars
- 235
- Forks
- 61
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 4
Description
With a debug build:
```
npm run build:wasi:debug
```
and test,
```
npm run test:wasi
```
the pipeline creates the result successfully, but on destructor cleanup:
```
1: Caused by:
1: 0: failed to invoke command default
1: 1: error while executing at wasm backtrace:
1: 0: 0xab50a - !dlfree
1: 1: 0xab410 - !free
1: 2: 0xa95a3 - !operator delete(void*)
1: 3: 0x258b66 - !itk::LightObject::~LightObject()
1: 4: 0x23f139 - !itk::LightObject::UnRegister() const
1: 5: 0x269bda - !__cxx_global_array_dtor.58
1: 6: 0xadc5a - !__funcs_on_exit
1: 7: 0xadbd8 - !__wasm_call_dtors
1: 8: 0x29be61 - !itk_wasm_delayed_exit
1: 9: 0x29beea - !_start
1: note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information
1: 2: wasm trap: out of bounds memory access
```
Contributor guide
Assessment
This issue has not been assessed yet.