Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2019.4
2019.4.0f1
2020.2
Issue ID
1254779
Regression
Yes
[ECS] “Out of memory” error in WebGL build when GameObject with multiple children objects has Convert To Entity Component
How to reproduce:
1. Open the attached project "1254779.zip"
2. Open the "Test" Scene
3. Build and run the WebGL Player
Expected result: an empty screen with a skybox is displayed
Actual result: a grey screen is displayed and after ~5 seconds "Out of memory" alert message appears
Reproducible with: 2019.4.8f1 (0.8.0-preview.8, 0.11.1-preview.4), 2020.1.2f1 (0.13.0-preview.24), 2020.2.0a20
Not reproducible with: 2018.4.26f1 (0.0.12-preview.24), 2019.4.8f1 (0.7.0-preview.19)
Notes:
- Only reproduces when Convert To Entity Component's parameter "Conversion Mode" is set to "Convert And Destroy"
- Only reproduces when the "EntityObj" GameObject has two or more Sphere GameObjects as its children
- Reproduces on Google Chrome (84.0.4147.105), Microsoft Edge (Chromium) (84.0.522.59), Firefox (79.0) web browsers
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
- 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
Resolution Note (fix version 2020.2):
An issue with the job system related to single threaded platforms was causing this crash, and has been resolved.
Resolution Note (fix version 2019.4):
This issue has been fixed and should no longer reproduce in Unity 2019.4.19f1 and above