DefaultRubyVM(module) crash using my own wasm file #259

jeezs · 2023-07-27T14:54:27Z

jeezs
Jul 27, 2023

I create a wasm file using the example found in the git :

curl -LO https://github.com/ruby/ruby.wasm/releases/latest/download/ruby-3_2-wasm32-unknown-wasi-full.tar.gz tar xfz ruby-3_2-wasm32-unknown-wasi-full.tar.gz mv 3_2-wasm32-unknown-wasi-full/usr/local/bin/ruby ruby.wasm mkdir src echo "require './src/my_file'\nputs 'Hello'" > src/my_app.rb echo "puts 'Hello from my REQUIRED file'" > src/my_file.rb wasi-vfs pack ruby.wasm --mapdir /src::./src --mapdir /usr::./3_2-wasm32-unknown-wasi-full/usr -o my-ruby-app.wasm wasmtime my-ruby-app.wasm -- /src/my_app.rb

then I try to execute the wasm file in the browser using the following code :

<html>

const buffer = await response.arrayBuffer();
    const module = await WebAssembly.compile(buffer);
    const {vm} = await DefaultRubyVM(module);
    vm.printVersion();
    vm.eval(`
    require "js"
    luckiness = ["Lucky", "Unlucky"].sample
    JS::eval("document.body.innerText = '#{luckiness}'")
  `);

};
main();

</script>
<body></body>
</html>

The lin e : const {vm} = await DefaultRubyVM(module); raise the error Unhandled Promise Rejection: TypeError: First argument to FinalizationRegistry should be a function
Maybe I use the wasm file the wrong way or is it a bug or Wasmtime and my wasm file have version compatibility problem . If someone have an idea? or is there another way to use my own wasm file within the browser?

Answered by jeezs

Jul 28, 2023

the version that causes trouble is wasi-vfs version 0.4.0.
So I switch to version 0.3.0.
latest version of browser.umd.js also conflict with any versions of wasi_vfs so I download this version instead : https://cdn.jsdelivr.net/npm/@ruby/wasm-wasi/dist/browser.umd.js,
Then it works.

View full answer

jeezs · 2023-07-28T09:06:27Z

jeezs
Jul 28, 2023
Author

Answering myself:
I was using the wrong install because I thought WASI is the same for JS and native, should install: ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz instead of : ruby-3_2-wasm32-unknown-wasi-full.tar.gz
The correct install script is :
`curl -LO https://github.com/ruby/ruby.wasm/releases/latest/download/ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz
tar xfz ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz

mv 3_2-wasm32-unknown-wasi-full-js/usr/local/bin/ruby ruby_js.wasm

mkdir src
echo "require './src/my_file'\nputs 'Hello from main file'" > src/my_app.rb
echo "puts 'Hello from my required file'" > src/my_file.rb

wasi-vfs pack ruby_js.wasm --mapdir /src::./src --mapdir /usr::./3_2-wasm32-unknown-wasi-full-js/usr -o my_js_app.wasm`

0 replies

jeezs · 2023-07-28T09:08:14Z

jeezs
Jul 28, 2023
Author

Now the problem is wasi-vfs that have problem with js profile. Hope it'll be solved soon.

0 replies

kateinoigakukun · 2023-07-28T16:29:21Z

kateinoigakukun
Jul 28, 2023
Maintainer

@jeezs Thank you for detailed report 🙏 Which version of wasi-vfs are you using?

0 replies

jeezs · 2023-07-28T20:02:41Z

jeezs
Jul 28, 2023
Author

the version that causes trouble is wasi-vfs version 0.4.0.
So I switch to version 0.3.0.
latest version of browser.umd.js also conflict with any versions of wasi_vfs so I download this version instead : https://cdn.jsdelivr.net/npm/@ruby/wasm-wasi/dist/browser.umd.js,
Then it works.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DefaultRubyVM(module) crash using my own wasm file #259

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

DefaultRubyVM(module) crash using my own wasm file #259

jeezs Jul 27, 2023

Replies: 4 comments

jeezs Jul 28, 2023 Author

jeezs Jul 28, 2023 Author

kateinoigakukun Jul 28, 2023 Maintainer

jeezs Jul 28, 2023 Author

jeezs
Jul 27, 2023

jeezs
Jul 28, 2023
Author

jeezs
Jul 28, 2023
Author

kateinoigakukun
Jul 28, 2023
Maintainer

jeezs
Jul 28, 2023
Author