Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
3
Found in
2022.1.0a12
Issue ID
1371445
Regression
Yes
[WebGL] Build fails to launch due to Runtime errors
How to reproduce:
1. create new project
2. add Sample Scene to build
3. Build&Run
4. Notice it runs
5. add a cube to your scene
6. Build&Run
7. NOTICE: build fails running with "Maximum call stacksize exceeded"
Reproduced with: 2022.1.0a12, 2021.2b16
Does not reproduce with: 2022.1.0a11, 2021.2b15
Error:
RuntimeError: memory access out of bounds
Workaround: make a Clean Build (Build dropdown in Build Settings)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment