Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out of memory: wasm memory #29778

Closed
xxyGoTop opened this issue Jan 17, 2019 · 2 comments
Closed

Out of memory: wasm memory #29778

xxyGoTop opened this issue Jan 17, 2019 · 2 comments
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@xxyGoTop
Copy link

What version of Go are you using (go version)?

$ go version
go.11.2

What did you do?

I wrote an animation, the first time it works fine, but after refreshing the browser multiple times, the program throws an exception.

I tried https://bobcob7.github.io/wasm-rotating-cube/
This problem will also occur

this errors:
RangeError: WebAssembly Instantiation: [Out of memory: wasm memory]

@agnivade
Copy link
Contributor

There are several issues here -

/cc @neelance for further comments.

@agnivade agnivade added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. arch-wasm WebAssembly issues labels Jan 17, 2019
@aykevl
Copy link

aykevl commented Jul 14, 2019

Just discovered this. I think it's a bug in Chrome because I have the same issue with an alternative WebAssembly compiler (after many reloads) and I never had it with Firefox.

If you ask me, all resources should be freed after a page is reloaded. Apparently Chrome doesn't do that (but does after closing/reopening the tab).

@golang golang locked and limited conversation to collaborators Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

4 participants