Hi there, I will like to report a bug with the Unity 2019 editor because it gets stuck a lot ( like 3 o 5 times every 8 hours) however, as I understand there are no repro steps to get it stuck.
Is any way to get a log of where it gets stuck or something ( like a memory footprint or log) to send a bug report? How do you report that kind of bugs?
Hello! You can find Editor logs here: Unity - Manual: Log files
When the Editor crashes, the logs will include crash stack which makes it easier to find out what caused the crash. If the Editor freezes and stops responding, it’s a bit harder to find the reason why, as the last entries in the log will be about what the engine did before freezing. I’d also recommend updating your OS and drivers, as the issue might not be directly related to the Editor.
If that still doesn’t help and you’ll submit a bug report, please post its case ID here.
@Suduckgames
Can you post your hardware / OS specs?
Thank you very much for your reply!
The problem is with the Editor Freezing, I will try updating the drivers and if the problem still persists I will open a bug report with the editor log.
@Antypodish
Sure, I have an Intel Core i7-8700, 32 GB of Ram, with a NVIDIA GeForce RTX 2080. I use windows 10 version 1809, SO version 17763.737
When editor gets frozen, you can no longer slide some parameter like location x or rotation in the UI.
I’m getting this a lot and it’s really terrible development UX. Going to try out 2019.3 to see if it’s any better.
Let me know if that helps so that I can consider an upgrade.
I didn’t have enough time to update drivers ( I know I should and I will!)
However, I noticed that in my case the stuck happens when the code is rebuilt in the editor.
I am using Visual Studio 2017, are you having the same problem?
Can I have this problem because I am not using the new visual studio?
@Suduckgames – Visual Studio 2019 seems better overall, upgraded recently - I was having similar issues with Unity locking up on occasion with VS 2017.
// WildStyle
I use Visual Studio 2019, and switching to 2019.3 beta fixed the glitches.
Of course, now there’s beta bugs to deal with (found a big one in b6 with a big name asset) but at least I can work without waiting for the editor to unlock.
I have updated my drivers and visual studio to 2019. However the problem persists,
It happens at the compilation of the code. I have opened the editor log and the last lines are these
- Starting compile Library/ScriptAssemblies/Assembly-CSharp-Editor.dll
[Logcat] [WorkThread] 12:09:17.2813 D:/Progamas/SDK\platform-tools\adb.exe devices
[Logcat] [WorkThread] 12:09:17.4767 List of devices attached
- Finished compile Library/ScriptAssemblies/Assembly-CSharp-Editor.dll
Assets\_Suduck\Localization\Editor\LocalizationWindow.cs(16,26): warning CS0414: The field 'LocalizationWindow.defaultLanguage' is assigned but its value is never used
Reloading assemblies after finishing script compilation.
Begin MonoManager ReloadAssembly
[Logcat] [MainThread]12:09:17.7769 OnDisable, Auto select: False
[Logcat] [WorkThread] 12:09:17.7849 Worker thread exited
[Logcat] [MainThread]12:09:17.7849 Dispatcher shutting down
Should I open a bug report? For me, the log seems pretty straightforward ( just recompiling the code), so I don’t think that with a bug report you can identify the problem. Any way I can give more information?
If this issue project-specific? if no, I don’t think that a project would help in this case since there are no real repro steps and the Editor freezes only after a few hours of work. What you could do is attach Visual Studio debugger to the Editor and then break the execution once it freezes, and send us the callstack. This should at least give an idea which area is involved, and what could be the cause of these freezes.