Anyone having trouble with memory in wasm?


I am using the new wasm-unknown-unknown target. My program contains two large binary asset that I ship using the include_bytes!.

When I run it a function the Chrome, supposed to return a pointer in memory, I receive
a pointer that is way off the memory buffer limit. Does somebody else experienced that?


Add to Cargo.toml

opt-level = 1

My small test call of include_bytes! worked after that.


Thank you! That did not solve my bug but that really looks like the issue I am experiencing.