Search Issue Tracker
Fixed
Votes
12
Found in
5.1.1f1
Issue ID
710749
Regression
No
Unity editor crashing when entering deep profiling
- Open scene Stage1 in attached project
- Open Profiler window and enable Deep Profile
- Press Play and after a few seconds Unity will crash
Comments (16)
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
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Coollinka
Sep 09, 2016 21:20
Unity 5.4.0f still broken!
djarcas
Feb 17, 2016 09:36
Aaaand 7 months later, it's still broken!
djarcas
Feb 03, 2016 15:31
100% repro on latest Unity...
Gladyon
Sep 13, 2015 18:49
Same issue with 5.02f1 32bits.
I also noted that there's a very large amount of memory used by Unity when 'Deep profile' is enabled.
In about 30s Unity eats about 2Go of RAM with 'Deep profile' active.
When no profiler or 'Deep profile' disabled, no memory leaks after several minutes (about 200Mo only for the Unity process and 550Mo with profiler on but deep profile disabled).
Note that it may be a case of GC not freeing memory soon enough before Unity reaches the 3Go...
AndrewCross
Aug 24, 2015 15:38
I'm also have the same issue. When it will be fixed?