Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0p3
Issue ID
866626
Regression
No
Profiler is using unusual amounts of memory leading to Fatal Error
Profiler is using unusual amounts of memory leading to Fatal Error. If you open profiler window with "Record" enabled and enter Play mode with the script that Loads Resources to memory the profiler uses unusual amounts of memory resulting in very long time entering Play mode or even fatal error.
Important notes:
1. Profiler settings: Record: ON; Deep Profile: OFF; Profile Editor: OFF; Active Profiler: OFF;
2. Assets load to memory as expected and huge amount of memory is not used when Record option in profiler is OFF;
To reproduce:
TEST 1:
1. Open project;
2. Open Profiler window;
3. Enable Record function on Profiler;
4. Enable Task Manager to keep an eye on memory usage.
5. Make sure "Load All Resources" script is enabled (located on "GameObject" game object);
6. Enter Play mode and wait for 30 seconds or so.
Note: Observe the increase of memory usage by Unity in the Task manager (picture: "Unity 5.5.0p4.png")
7. Wait about 10 minutes or so.
Note: Fatal error (picture: "FatalError.png");
TEST 2:
1. Repeat the first 5 steps of TEST 1.
2. Delete folder "Headgear" (Resources --> Headgear);
3. Enter Play mode and wait for 20 seconds or so;
Note: This time the script will only need to load 34 meshes to memory.
Note: Editor enters play mode, but profiler is using about 1.7 Gb of memory at first and then drops down to about 0.8 Gb (picture: "Unity 5.5.0p4 (fewer meshes).png");
4. Disable the "Load All Resources" script.
5. Enter Play mode.
Note: Task manager still shows that unity is using an unusual amount of memory.
6. Exit Play mode and Close the Editor.
7. Open the same project;
8. Enter Play mode with "Load All Resources" script disabled;
9. Unity is back on using normal amounts of memory.
Reproduces with: 5.5.0p3; 5.5.0p4; 5.6.0b3; 5.6.0b5;
Doesn't reproduce with 5.3.6f1; 5.4.3p3; (Editor simply runs out of samples, picture: "Unity 5.3.6f1.png");
Note: Repro projects for this case (one for 5.3.6f1 and one for 5.5.0p3) are stored in OwnCloud (two projects, both take about 50 Mb of disk space each).
Link:
https://oc.unity3d.com/index.php/s/cErFdwYoIfWBPHy
Password:
626668
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment