Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
1
Found in
6000.0.68f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134696
Regression
No
Too little validation messages in the "WebAssembly Language Features" Memory settings
How to reproduce:
1. Create a new Unity project
2. In the Build Settings, switch to the "Web" Platform
3. Go to Edit -> Project Settings -> Player -> Web settings -> Publishing Settings -> WebAssembly Language Features
4. Set the "Initial Memory Size" field to 1 and observe the results
Expected results: The warning is thrown or shown in the box that the configuration is not appropriate
Actual results: No validation messages are shown and build fails with the "emcc: warning: -pthread + ALLOW_MEMORY_GROWTH may run non-wasm code slowly" error
Reproducible with: 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.