Steps to reproduce:

1. Open the attached index.html in Firefox 91.10.0esr (32-bit) and notice:
   Status: Compiled
   The answer to life itself: 42

2. Click on the button labeled "Reload" next to "Remove the iframe and add it again" and notice the same output as in "1".

3. Repeat "2" until the following output is observed (for me it happens after around ~10 times):
   Status: Compiling...
   The answer to life itself:

4. Open the Developer Tools and notice in Console: "Uncaught out of memory"

Actual results:

An "out of memory" error occurred.

Expected results:

It should be possible to repeatedly add/remove an iframe containing Wasm without an out of memory occurring.

The issue seems to be specific to 32-bit versions. I could reproduce it with Firefox 101.0 (32-bit) too, but not with 91.10.0esr (64-bit) or 101.0 (64-bit).

Managed to reproduce on Windows 10 x32, the issue is not reproducible on Windows 10 x64.

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:bvisness, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Backed out changeset fd3606f15938 (bug 1773225) for causing spidermonkey bustages in ArrayBufferObject.cpp

Backout: https://hg.mozilla.org/integration/autoland/rev/61a5e77067ce509969ee4ea18bb849ce775ef615

Failure push: https://treeherder.mozilla.org/jobs?repo=autoland&revision=fd3606f159389e376883c85163448165bc9975ac&selectedTaskRun=FteozoJqTtuO_-hGf6veFw.0

Failure log: https://treeherder.mozilla.org/logviewer?job_id=404894267&repo=autoland&lineNumber=3164

https://hg.mozilla.org/mozilla-central/rev/e74de6e39fdb

Reproduce the issue with Windows 10x64 Firefox 91.10.0esr (32-bit).
Verified as fixed with Windows 10x64, Firefox Nightly 112.0a1(32-bit) and 111.0b7 (32-bit).