Search Issue Tracker
Fixed
Fixed in 6000.6.0a1
Fix In Review for 6000.3.13f1, 6000.4.2f1, 6000.5.0b2
In Progress in 6000.0.X
Votes
1
Found in
6000.0.68f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134687
Regression
No
Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
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 a negative number and observe the results
Expected results: Field validation doesn't allow negative numbers
Actual results: Negative numbers can be entered
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
Notes:
- Affects all Memory-related fields
- Build fails when the fields are set to the negative numbers
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.4.2f1):
Fixed in 6000.4.2f1
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1