Question

141

using WebAssembly in chrome extension

rated 0 times [ 142] [ 1] / answers: 1 / hits: 15518 / 6 Years ago, mon, april 2, 2018, 12:00:00

I have a chrome extension that includes a complicated function comp_func(data) which takes a lot of CPU by performing many bitwise operations. Because of that, I'm trying to use WebAssembly.

I've tried to follow several tutorials, for example this one and this one.

The first link says:

fetch('simple.wasm').then(response =>

  response.arrayBuffer()

).then(bytes =>

  WebAssembly.instantiate(bytes, importObject)

).then(results => {

  results.instance.exports.exported_func();

});

but I get an error:

Uncaught (in promise) TypeError: WebAssembly Instantiation: Import #0 module="env" error: module is not an object or function

I've tried a lot to use this approach, but it didn't work. I can't understand how to use WebAssembly that is loaded from the .wasm file.

So I've tried an easier approach:
The second link says to put this line in the html file:

<script src="index.js"></script>

and then just use the exported function:

var result = _roll_dice();

BUT, I'm in an extension so I only have a background.html file.
So I'm looking for a way to access the Module which was loaded in the background file.
And things get complicated, because the function comp_func(data) is called from a Worker.

This is what I've tried so far:

If I call chrome.extension.getBackgroundPage() I can access the Module
but I can't send it to the Worker:

Failed to execute 'postMessage' on 'Worker': # could not be cloned.

And if I try to stringify it first:

Uncaught TypeError: Converting circular structure to JSON

(I tried to un-circular it, didn't work...)

And I can't call chrome.extension.getBackgroundPage() from the Worker because I can't access chrome API from there.

So my questions are:

Did someone try to load .wasm file in chrome extension and succeed?
The second approach (loading the js file) sounds simpler but if you have a working example for this approach it would be great.

or 2. How to access the Module that has been loaded in background.html (from the second example)?

or 3. How to pass the functions that I needed from the js file to the Worker (via postMessage)?

To summarize, did someone try to use WebAssembly in a chrome extension and survive to tell?

EDIT:
I eventually left the approach of WebAssembly.
I also posted this question at bugs-chromium,
and after few month got an answer. Not sure if this is really working, but maybe this, along with the marked answer, will help someone.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

jenamackennac

Add To Favorites

Follow

Total Points: 304

Total Questions: 110

Total Answers: 107

Location: Ecuador

Member since Thu, Jun 4, 2020

4 Years ago

jenamackennac questions

1 React render PDF file inside component based on API response

Fri, Feb 18, 22, 00:00, 2 Years ago

1 Webpack error: configuration.module.rules[0] has an unknown property 'query'

Mon, Aug 30, 21, 00:00, 3 Years ago

1 Vue is not defined/not a constructor

Wed, Apr 21, 21, 00:00, 3 Years ago

1 WebView2 - Get an attribute

Thu, Apr 1, 21, 00:00, 3 Years ago

1 IntersectionObserver API and TypeScript

Tue, Feb 2, 21, 00:00, 3 Years ago

View All

answered 6 Years ago leilanichasel · Accepted Answer

I've been fiddling with WebAssembly recently, and found a way to make it work. Here are the script files:

main.js

chrome.browserAction.onClicked.addListener(function(tab) {

 chrome.tabs.executeScript(null, {file: "content_script.js"});

});

content_script.js

  var importObject = { imports: { imported_func: arg => console.log(arg) } };

  url = 'data:application/wasm;base64,' + "AGFzbQEAAAABCAJgAX8AYAAAAhkBB2ltcG9ydHMNaW1wb3J0ZWRfZnVuYwAAAwIBAQcRAQ1leHBvcnRlZF9mdW5jAAEKCAEGAEEqEAAL";

  WebAssembly.instantiateStreaming(fetch(url), importObject)

  .then(obj => obj.instance.exports.exported_func());

The data URL belongs to the common tutorial wasm sample (simple.wasm), which writes 42 on the console.

PS. If it seems like cheating or bad practice to you, this content_script.js also works:

var importObject = {

   imports: {

    imported_func: function(arg) {

    console.log(arg);

    }

   }

 };



var response = null;

var bytes = null;

var results = null;





var wasmPath = chrome.runtime.getURL("simple.wasm");

fetch(wasmPath).then(response =>

    response.arrayBuffer()

    ).then(bytes =>

       WebAssembly.instantiate(bytes, importObject)

        ).then(results => {

        results.instance.exports.exported_func();

  });

Only if you include the code files in the web_accessible_resources section in manifest.json, though:

    ...

    "web_accessible_resources": [

     "content_script.js",

     "main.js",

     "simple.wasm"

    ],

    ...

Github: https://github.com/inflatablegrade/Extension-with-WASM

It can also be made compatible with Manifest V3.