Hi. I’m working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it.
After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I’m kinda new to Node I was only able to understand that it was happening after the call to the exported WASM method returned.
This happened almost two months ago, and while I thought about reporting this to the node devs (WASI’s also experimental), I was going to move soon and a lot has gone on.
Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don’t have access to right now) but I wasn’t able to.
I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I’m also on Gentoo now, while I was running Arch previously.
Unfortunately I don’t have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.
This situation is upsetting. I don’t know what’s changed that caused the problem to “disappear”, so i feel uncomfortable considering this solved. What would be the best approach in this situation?
EDIT: I also just tested it on Debian live, and I still wasn’t able to reproduce the segfault
I’d keep going until you see it again and try to solve it then. I wouldn’t report an issue that you can’t reproduce, some projects refuse to accept issues without a repro. Sometimes something weird happens and you don’t know why and you’ll never know, you just need to move on and keep building, if it’s a real problem it’ll come back.
i think i’ll submit a report with the exact info of the other environment, when i’ll get back at it. for now i’ll keep going.
as another comment is saying, if it’s not useful they’ll just ignore it.