Search Issue Tracker
By Design
Votes
1
Found in
2017.1.0f3
Issue ID
950310
Regression
No
Freeze after recompiling scripts and trying to make any changes in the editor
How to reproduce:
1. Open attached Unity project "Laircraft"
2. Load scene "Main Scene"
3. Enter Play mode
4. Stop Play mode
5. Load any script related to the "Main Scene" scene
6. Make any code change to trigger a recompile
7. Save changes
8. Enter Play mode or do any other changes in the scene
Repeat 6-8 steps if editor is not freezing
Expected Result: Editor is not freezing after making changes in code.
Actual Results: Unity freezes when making any changes in the editor after recompiling scripts.
Reproducible with: 2018.1.0a2, 2017.3.0b7, 2017.2.0p1, 2017.1.2p2, 5.6.4p1, 5.5.5p1.
Workaround: Reload Unity and enter Play mode.
Reproduced on:
- AMD A6-7400K Radeon R5, 6 Compute Cores 2C+4G; Windows 10 Pro 64-bit;
- [User] CPU: i7-6700k 4GHz, RAM 16GB (can't remember the speed), GPU: NVIDIA GeForce GTX 1050 Ti, HDD: Crucial_CT525MX300SSD1 (SSD), Board: FX305.
Note: Reproducible only in the scene which contains massive scripts.
Comments (1)
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Mikael-H
Jun 19, 2018 06:16
Is it by design that the editor should freeze and need a restart?
We are in a project (which also has a huge code base) and we have the same issue. We are on Unity 5.6 and I was hoping that upgrading would solve this issue but as this has been reproduced on 2018.1 maybe that's not the case..