Search Issue Tracker
Fixed in 5.1.0
Votes
0
Found in
5.0.0f4
Issue ID
680020
Regression
No
Unity Not Responding after leaving it at idle for a few hours
Unity Not Responding after leaving it at idle for a few hours.
Unity becomes unresponsive (hangs) when left alone for a few hours.
This happens on the OSX as well as Windows. This occurs when Unity is left at idel (not in play mode) for a few hours.
I have narrowed this down to potential use of the profiler where if I don't use the profiler and leave Unity for a few hours it is fine. But if the profiler was used, then a few hours later Unity will be frozen and require killing the task or force quit on OSX.
It doesn't matter what project is loaded or scene.
Comments (3)
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
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
- [UVCS] Popups in permissions window are sent behind the permissions view.
Apositive1
Oct 12, 2016 22:16
Happening to me as well. on 5.3.6f1 Getting hanging after about 15 hours.
SketchWork
May 06, 2016 20:27
Yes, this is still happening all the time. Even on latest version 5.3.4 P6.
Sven Uilhoorn
Dec 08, 2015 17:09
I've just installed Unity for the first time and this still happens for me. Installed 5.1, 5.2 and today 5.3.0f4, all win7 64-bit, and all hang after about 10 minutes on an empty project.