Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a12
Issue ID
1108361
Regression
No
WASM memory growth is broken if threadsSupport is enabled
-e: see title, build works when adding a specific memory size
--this is a regression in emscripten itself
-repro:
--open attached project
--build&run for webgl
--notice it works
--open Editor\EnableThreads.cs
--remove "PlayerSettings.WebGL.memorySize = 512;"
--recompile
--build and run
--NOTICE build fails in browser with error:
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2019.3.X):
This is currently expected behavior. Wasm multithreading does not currently support memory growth, but one must use a fixed size. We should document this as a limitation. Wasm working group is in the middle of speccing this scenario, after which the fix will propagate its way to Emscripten for us to utilize.