Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0p5
Issue ID
955246
Regression
No
WebAssembly built game does not work if WebGL Memory size is not multiple of 16
How to reproduce:
1. Create new empty project file
2. Switch to WebGL platform
3. In Player, Settings mark WebAssembly(experience) true and set WebGL Memory Size higher than default (for example 400mb)
4. Build Game and open in browser
Expected result: Game opens without errors
Actual result: Game didn't work, error appears: "Uncaught (in promise) LinkError: WebAssembly Instantiation: memory import 540 has larger maximum than maximum 6560, got 6656"
Reproduced with: 5.6.4f1, 2017.1.2f1, 2017.2.0f3, 2017.3.0b4
Reproduced with: Chrome, Firefox, Safari
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment