cmd/compile: wasm: LinkError: "data segment does not fit in memory"

[Splizard]

There is a regression from 1.12 to 1.13, a program that successfully compiles and runs on Firefox and Google Chrome in Go 1.12 will not run when compiled with Go 1.13

Firefox gives the error:

LinkError: "data segment does not fit in memory"

Google Chrome gives the error:

LinkError: WebAssembly.instantiate(): data segment is out of bounds

The project is quite large and the Web Assembly file is ~50mb when uncompressed.

I'm happy to provide further details on request, however, I don't have a trivial program that reproduces this.
I am using the appropriate wasm_exec files for both versions.

[agnivade]

Thanks @Splizard. It will be very helpful to have further details for us to debug this further.

Since it is readily reproducible for you, may I also ask you to run a git bisect and check which commit introduced this regression. I understand this is a time taking request, but if we know which commit caused this, it may give us an idea as to what went wrong.

[agnivade]

@neelance @cherrymui

[neelance]

This is most likely due to 460f9c6. Could you please check if increasing the initialSize solves the issue?

[janpfeifer]

Same problem here (main.wasm is 33Mb size), and my project won't run on go 1.13.

Is there a flag way to change initialSize, or does one has to recompile wasm ?

[agnivade]

You have to recompile the Go distribution with the new initialSize.

[janpfeifer]

Thanks Agniva.

I tried recompiling setting it to 128Mb and it still failed. When I changed it to 1 GB it got back working.

Changing initialSize to 128Mb, cleaning and then recompiling my code worked :)

[neelance]

Let's try to come up with a minimal example that triggers this bug. Maybe a large global array?

[gopherbot]

Change https://golang.org/cl/199358 mentions this issue: cmd/link: produce valid binaries with large data section on wasm