Unity Editor UI keeps reloading something after each click

Hi Guys

I very regularly get this, just from clicking in project settings, without changing any settings.


What is this and why am I getting it? Hard to be productive when this pops up every few clicks

 

For example I highlighted a HDRP Quality asset in Assets > Settings, hit CTRL+D to duplicate it. That should be instant, but this came up and was sitting there for about 30 seconds:

 

64GB Ram
12 core i7
RTX 2070 Super
Windows 10 Pro 20H2
NVidia Studio driver 461.40
SSD drive for OS and this project

 

Simply selecting the Main Camera in the HDRP Template scene:

 

Anybody?

 

I have been getting the same. I am using 2020.2 though.There was a change in how Unity does messages to let you know what it is doing other than just saying hold on, my guess is that it is related to that change.

This causes some problems that I have run into to. If I am writing software in visual studio 2019, save and then switch back to unity. Sometimes the unity editor will compile the code other times I will have to minimize/ maximize unity to get the unity editor to recognize code changes have taken place. (I have set the correct setting in visual studio and unity for auto refresh but does not seem to change anything)

I mention this because they may be related. Its as if the unity editor is going into some sort of aggressive sleep mode, which could explain the repaint message you are getting.

I have not submitted a bug report yet since I am not sure if I am missing some setting in Unity or the OS

 

You should try to turn on the profiler in editor mode, so you get some clue about what's causing the slowdown. It's probably a Unity bug, but unless it's happening with everyone, a bug saying "sometimes something is causing a slowdown" isn't very easy to investigate.

 

Sorry for the late reply took me a min to find that file

Code (CSharp):

1. [Performance] GameView.Paint                                                             :   130716 samples, Peak.   125 ms (45.7x), Avg.  2.73 ms, Total. 356.8 s (2.8%)
2. [Performance] GameView.Repaint                                                           :   130716 samples, Peak.   125 ms (46.0x), Avg.  2.71 ms, Total. 354.0 s (2.8%)
3. [Performance] GameView.OnGUI.Layout                                                      :   130726 samples, Peak.  28.0 ms (113.4x), Avg.   247 us, Total. 32.27 s (0.3%)
4. [Performance] GameView.OnGUI.repaint                                                     :   130716 samples, Peak.   103 ms (52.5x), Avg.  1.96 ms, Total. 255.7 s (2.0%)
5. [Performance] SceneView.Paint                                                            :   119698 samples, Peak.  2.44 s (611.4x), Avg.  3.99 ms, Total. 477.1 s (3.8%)
6. [Performance] SceneView.Repaint                                                          :   119698 samples, Peak.  2.44 s (650.6x), Avg.  3.75 ms, Total. 448.3 s (3.6%)
7. [Performance] SceneView.OnGUI.Layout                                                     :   119776 samples, Peak.   102 ms (268.2x), Avg.   379 us, Total. 45.36 s (0.4%)
8. [Performance] SceneView.OnGUI.repaint                                                    :   119697 samples, Peak.   129 ms (45.7x), Avg.  2.82 ms, Total. 338.1 s (2.7%)
9. [Performance] GizmoManager.DrawGizmos                                                    :   239394 samples, Peak.  4.83 ms (93.2x), Avg.  51.8 us, Total. 12.40 s (0.1%)

Code (CSharp):

1. Performance] GizmoManager.RecalculateGizmos                                             :      219 samples, Peak.   343 us (7.9x), Avg.  43.6 us, Total. 9.559 ms (0.0%)
2. [Performance] Toolbar.Paint                                                              :     1175 samples, Peak.  32.9 ms (14.4x), Avg.  2.29 ms, Total. 2.688 s (0.0%)
3. [Performance] Toolbar.Repaint                                                            :     1175 samples, Peak.  32.9 ms (17.6x), Avg.  1.87 ms, Total. 2.192 s (0.0%)
4. [Performance] ProjectBrowser.Paint                                                       :     1434 samples, Peak.  1.04 s (104.3x), Avg.  9.94 ms, Total. 14.26 s (0.1%)
5. [Performance] ProjectBrowser.Repaint                                                     :     1434 samples, Peak.  1.04 s (108.0x), Avg.  9.61 ms, Total. 13.78 s (0.1%)
6. [Performance] ProjectBrowser.OnGUI.Layout                                                :     1837 samples, Peak.   153 ms (56.1x), Avg.  2.73 ms, Total. 5.014 s (0.0%)
7. [Performance] ProjectBrowser.OnGUI.repaint                                               :     1432 samples, Peak.  28.5 ms (6.3x), Avg.  4.54 ms, Total. 6.506 s (0.1%)
8. [Performance] SceneHierarchyWindow.Paint                                                 :     2714 samples, Peak.  3.41 s (493.0x), Avg.  6.93 ms, Total. 18.80 s (0.1%)
9. [Performance] SceneHierarchyWindow.Repaint                                               :     2714 samples, Peak.  3.41 s (502.9x), Avg.  6.79 ms, Total. 18.43 s (0.1%)

Code (CSharp):

1. [Performance] ConsoleWindow.OnGUI.repaint                                                :      425 samples, Peak.  3.04 ms (3.7x), Avg.   811 us, Total. 344.7 ms (0.0%)
2. [Performance] InspectorWindow.Paint                                                      :     3023 samples, Peak.  1.16 s (90.3x), Avg.  12.9 ms, Total. 38.89 s (0.3%)
3. [Performance] InspectorWindow.Repaint                                                    :     3023 samples, Peak.  1.16 s (91.6x), Avg.  12.7 ms, Total. 38.34 s (0.3%)
4. [Performance] InspectorWindow.OnGUI.Layout                                               :     3120 samples, Peak.  22.0 ms (264.7x), Avg.  83.1 us, Total. 259.4 ms (0.0%)
5. [Performance] InspectorWindow.OnGUI.repaint                                              :     3020 samples, Peak.  9.30 us (11.5x), Avg.   812 ns, Total. 2.452 ms (0.0%)
6. [Performance] Application.InvokeFinishedLoadingProject                                   :        1 samples, Peak.  46.5 ms (1.0x), Avg.  46.5 ms, Total. 46.53 ms (0.0%)
7. [Performance] ProcessService.OnProjectLoaded                                             :        1 samples, Peak.  40.9 ms (1.0x), Avg.  40.9 ms, Total. 40.86 ms (0.0%)
8. [Performance] Application.InvokeProjectWasLoaded                                         :        1 samples, Peak.  1.00 ms (1.0x), Avg.  1.00 ms, Total. 1.002 ms (0.0%)
9. [Performance] Application.Message                                                        :  3252164 samples, Peak.  8.31 s (176190.0x), Avg.  47.1 us, Total. 153.3 s (1.2%)
10. [Performance] Application.Message.WM_00060                                               :      930 samples, Peak.   570 us (9.9x), Avg.  57.8 us, Total. 53.78 ms (0.0%)
11. [Performance] Application.Message.MouseMove                                              :    47659 samples, Peak.  1.53 s (2088.1x), Avg.   733 us, Total. 34.92 s (0.3%)
12. [Performance] ProjectBrowser.Ignore                                                      :     1284 samples, Peak.  1.70 us (2.0x), Avg.   859 ns, Total. 1.104 ms (0.0%)
13. [Performance] Application.Tick                                                           :  3253495 samples, Peak.  4.86 s (7679.3x), Avg.   633 us, Total. 2.059 ks (16.4%)

Code (CSharp):

1. [Performance] Application.TickSceneTracker                                               :  3253495 samples, Peak.   728 ms (5246.2x), Avg.   139 us, Total. 451.4 s (3.6%)
2. [Performance] EditorApplication.update                                                   :  3253495 samples, Peak.   724 ms (5899.1x), Avg.   123 us, Total. 399.4 s (3.2%)
3. [Performance] ConsoleLog.Tick                                                            :    61409 samples, Peak.   404 us (126.8x), Avg.  3.19 us, Total. 195.7 ms (0.0%)
4. [Performance] HierarchyWindow.Tick                                                       :    17222 samples, Peak.  10.7 ms (2868.4x), Avg.  3.72 us, Total. 64.10 ms (0.0%)
5. [Performance] Inspector.Tick                                                             :    17222 samples, Peak.  34.8 ms (246.1x), Avg.   141 us, Total. 2.436 s (0.0%)
6. [Performance] Tooltip.Tick                                                               :   238147 samples, Peak.  37.2 ms (1027.4x), Avg.  36.2 us, Total. 8.624 s (0.1%)
7. [Performance] Application.RequestRepaintForPanels                                        :   589194 samples, Peak.   742 us (132.0x), Avg.  5.62 us, Total. 3.312 s (0.0%)
8. [Performance] Application.UpdateScene                                                    :   589194 samples, Peak.   608 ms (385.2x), Avg.  1.58 ms, Total. 929.7 s (7.4%)
9. [Performance] GUIView.RepaintAll.PlayerLoopController                                    :   130609 samples, Peak.   607 ms (93.7x), Avg.  6.48 ms, Total. 846.3 s (6.7%)

Code (CSharp):

1. [Performance] Application.UpdateTextureStreaming                                         :   324513 samples, Peak.  16.1 us (42.7x), Avg.   377 ns, Total. 122.5 ms (0.0%)
2. [Performance] Application.UpdateVideoTextures                                            :   324513 samples, Peak.  85.8 us (330.2x), Avg.   260 ns, Total. 84.33 ms (0.0%)
3. [Performance] PackageImporter.Tick                                                       :    61393 samples, Peak.   125 us (177.3x), Avg.   703 ns, Total. 43.14 ms (0.0%)
4. [Performance] InspectorBackground.Tick                                                   :    81591 samples, Peak.  15.3 us (17.7x), Avg.   866 ns, Total. 70.62 ms (0.0%)
5. [Performance] Application.ChangeLayoutIfNeeded                                           :  3253495 samples, Peak.  3.28 ms (13362.1x), Avg.   246 ns, Total. 799.2 ms (0.0%)
6. [Performance] AsyncReadManager.ForceCloseFiles                                           :    12413 samples, Peak.   278 us (103.1x), Avg.  2.70 us, Total. 33.47 ms (0.0%)
7. [Performance] GUIView.RepaintAll.RepaintScene                                            :   458605 samples, Peak.  4.86 s (7543.2x), Avg.   644 us, Total. 295.3 s (2.3%)
8. [Performance] Application.Message.Timer                                                  :      891 samples, Peak.  93.9 us (7.6x), Avg.  12.4 us, Total. 11.06 ms (0.0%)
9. [Performance] Application.Idle                                                           :  2943915 samples, Peak.  34.8 ms (10.0x), Avg.  3.47 ms, Total. 10.20 ks (81.1%)

Code (CSharp):

1. [Performance] Application.Message.WM_00203                                               :       22 samples, Peak.  8.31 s (15.1x), Avg.   550 ms, Total. 12.10 s (0.1%)
2. [Performance] InactiveGI.Tick                                                            :    38851 samples, Peak.  1.12 ms (20.9x), Avg.  53.6 us, Total. 2.082 s (0.0%)
3. [Performance] RequestRepaintForPanels                                                    :  2664301 samples, Peak.  1.07 ms (257.2x), Avg.  4.16 us, Total. 11.10 s (0.1%)
4. [Performance] GUIView.RepaintAll.RequestRepaint                                          :  2664301 samples, Peak.   551 ms (14335.4x), Avg.  38.5 us, Total. 102.5 s (0.8%)

 

Thanks I submitted the bug report, just waiting on the issue ID now.

Its a quirky issue more of an annoyance than anything. My guess is that I am floating around some edge case from using four monitors, I have four monitor layout setup for Unity and I switch between Visual studio 2019 and unity through the task bar. I put all of that info in the bug report along with a screenshot.

 

This has been quite frustrating for me too, it really slows down the iteration speed and makes the overall UX frustrating
After every single time I open Unity it takes 5-7 mins just to open and to import something during that although nothing's changed, it even has to do script compilation at each startup for some reason
Also when clicking anything in the hierarchy it takes quite a long time to respond

I had been wondering if my system had slowed down but then I checked it with older versions of unity and it was fine

 

Can you tell me how I can share this, I have no idea where the log files are either
Also, I don't think I can submit a particular project because it is tied to unity versions and not the project itself

 

Case ID 1313824

issue tracker webpage

I will create a better project if I am able to better reproduce the issue. Its almost as if the Unity editor when losses focus (click on another application or minimize) and I try to click back onto Unity it does not want to refocus or does focus but into to some weird state, hence the unity editor does not see the script code changes or when you click on the assets in the hierarchy the gui.repaint message appears.

I feel like I am not being very helpful here... but I will try a few more experiments to see if I can more reliably reproduce the issue with steps

 

I had a similar issue in our project that I couldn't reproduce in a separate clean project. The Unity would start showing a busy message if I open a popup list in animation panel or context menu in Project window.

 

Are any of u using HDRP with Vulkan api? This combination causes similar symptoms to what u describe (with the exception that 90% of the time the editor never unlocks again I have to manually kill it).
It's probably unrelated but just in case.

 

Does anyone actually use 2020.x ? "Hold on busy (for ...s)" seems to be a non-stop occurrence. I've actually got work to do. Sticking to LTS.

 

This is really frustrating. Can we please have any update on this?

 

Getting this also. Often waiting on a progress bar after clicking an inspector or moving a prefab/gameobject

 

Any Update to this ?
I'm having this the last several versions after the 2019 LTS one.
Now I am trying 2021.x.

I created a new project yesterday and added one simple script with 10 lines of code and 5 empty gameobjects and a simple Scroll Rect mechnism.
And while doing so every sinlge change in code or hitting play take 10 seconds for refreshing/compiling.
I have a high-end rig, so dont tell me about hardware.
I just upgraded to better hardware in between switch between Unity versions.
I had no issue with much lower hardware while using 2019 LTS or (some) of the 2020.x versions.

What is it actually doing there?
You can say the project is empty, its super annoying and makes me lose interest in using Unity any further like this.

 

Yup. Also happens whenever I change my code and save using Visual Code. I also need to bring up the unity tab for it to recognize the code changes and start doing the reload.

 

@MartinTilo Trying not to be rude here (truly) but I think you're missing the point. Having to profile my app makes sense and is part of using any engine, but having to profile the editor is not something I would expect in a major release. Something fairly big changed after 2019LTS which has made the Editor nigh on unusable. I'm using the same assets and codebase as I am in 2019LTS but in 2020.x everything just causes this 'busy' message. We use Unity as a tool and shouldn't be expected to have to put up with an issue that's so obviously counterproductive to an efficient workflow. Makes me really worried for the future of the engine.

 

Like I mentioned, I'm not even getting to the part of MY app yet. Simply opening the HDRP template and clicking on things...

 

I have the same issue. Running 2020.2.1
It was after setting up the microsplat asset. Because before it was running with no major problem.

 

Thanks @MartinTilo Very much appreciate the thorough and thoughtful response, and for you taking the time to join in the discussions on this thread.

 

Well I just deleted the project and got the git backup

 

For scene view and GUI takes the longes. Using HDRP 11 package only.

Code (CSharp):

1. [Performance] Application.UpdateScene: 82123 samples, Peak.  3.66 s (633.3x), Avg.  5.77 ms, Total. 474.0 s (65.8%)
2. [Performance] GUIView.RepaintAll.PlayerLoopController: 53613 samples, Peak.  3.63 s (431.5x), Avg.  8.42 ms, Total. 451.3 s (62.6%)
3. [Performance] SceneView.Paint:  50325 samples, Peak.  3.63 s (476.3x), Avg.  7.62 ms, Total. 383.4 s (53.2%)
4. [Performance] SceneView.Repaint:  50325 samples, Peak.  3.63 s (478.8x), Avg.  7.58 ms, Total. 381.4 s (52.9%)
5. [Performance] SceneView.OnGUI.Layout:50608 samples, Peak.  43.6 ms (70.5x), Avg.   619 us, Total. 31.31 s (4.3%)
6. [Performance] SceneView.OnGUI.repaint: 50312 samples, Peak.  1.15 s (194.3x), Avg.  5.93 ms, Total. 298.5 s (41.4%)
7. [Performance] Application.Tick:  82123 samples, Peak.  8.09 s (1298.5x), Avg.  6.23 ms, Total. 511.7 s (71.0%)

Compiling scripts is taking longer and longer.

 

I know you are trying to do your job and I know us users are awful and ungrateful (I am not being sarcastic, I genuinely know the pain of working in your kind of role and I am genuinely sympathizing). That said...

The fact that Unity Employees working on profiling tooling are unaware of one of the most popular terrain/shader optimization tools on the Asset Store. A tool published by an accomplished AAA developer. A tool published by someone who has a reputation for working with Unity to help them engage better with assert publishers is, frankly, the problem.

I respectfully suggest that your manager ensures all their team have time to go and build spike projects using the most popular assets on the store. There aren't many of them, cover the top 10 and you will cover 90% of the pain us users are experiencing. Do it before you slap LTS on a release and we won't have to spend an age submitting bug reports.

Oh, and by the way, I am pretty certain the problems in this thread have NOTHING to do with third party assets.

Even as tiny Indie with no license fee for Unity I spend thousands in your store every year. I expect a LTS to save me time not cost it.

 

Our team has projects in 2019 LTS and projects in 2020.2 (And this week or next, our team will migrate some to 2020LTS)

but one thing I noticed is that in 2019.x and earlier, there were no interruption warnings on the screen ... from 2020 this started to happen. And I believe that it is precisely about this warning that people are commenting... in a way in 2019, the editor did the same things, but it was disguised, and the editor was not paralyzed. But in 2020, these warnings occur all the time, and freeze the editor.

In my case, the most time consuming is the load of the unity layout (If I'm not mistaken, the rebuild.UI or layout.Rebuild or something like that) This element is extremely time consuming to load. In terms of scripting, this also occurs, but it was already expected... still, it takes time.

In general, the iteration time is now shorter ... it would be nice if some of these jobs were done in the background, so as not to interrupt our workflow.

 

Thanks...
I just changed this setting to 0.1 and I already felt the difference. it's better this way.



But why is this setting set to 3 by default?

This value is too big to be standard, as I said, the editor interrupts for almost anything. Waiting 3 seconds "for everything" is not a good thing.

I also realized that this setting is not in the documentation yet. it would be good to include it


Thanks again, this will really speed things up here

 

some people complained that it pops up too often. And that sometimes it pops for a second then goes away. That's why. This really tells you there's no right solution, what some people like, others dislike.

 

I think what that config does is to delay the popping up of the dialog until a process blocks the UI for at least the configured time.

 

Yes, so setting it to smaller values should actually make the dialog pop up more often. 3 seconds seems like a sensible value.

 

I understand from the description of this button that apparently it will wait so many seconds after the editor returns from a defrost... That's why now these warnings just flash on my screen eventually.

But for me, it seemed that the warning ends faster, the lower this value, I realized this in 2020.3.0f ... this is strange.

 

Same here, I don't do anything and this thing keeps popping up
https://drive.google.com/file/d/1oAsEdCobRmH7BK5KUhiGpDChpft-mVlP/view?usp=sharing

 

This thread is particularly tone deaf. The problem is NOT that a window pops up to say "Busy" it's that the editor is unreasonably busy.

I recently took the time to reimplement my problematic project in 2019 - it was just a spike project to see if I wanted to update our main project to 2020 LTS yet. That spike is now MORE complex (as in more code and more imported assets) than the 2020 version and I do NOT have the unreasonable wait times I experience in the 2020 version.

Changing the time a dialog is displayed does not change the editor performance. Sure we can help profile problems with edge case bugs. But judging by the number of people hitting performance problems in 2020 I'd say this is not an edge case.

Pointing at asset devs, which is frankly common behaviour for Unity, is disrespectful. While I can accept there will be problematic assets out there (my own editor tools have been known to cause problems, for sure) it actually starts with Unity. If Unity wants to leverage the strength of the Asset Store then Unity MUST support those devs, not blame them for regressions.

 

I just got this error in the Unity console:

Code (CSharp):

1. An infinite import loop has been detected. The following Assets were imported multiple times, but no changes to them have been detected. Please check if any custom code is trying to import them:
2. Assets/Video Recordings/Grand Theft Amphibian/2021-03-27 21-40-07.mp4
3. Assets/Video Recordings/Grand Theft Amphibian/2021-03-27 11-01-08.mp4
4. Assets/Video Recordings/Grand Theft Amphibian/2021-03-27 11-01-17.mp4
5. Assets/Video Recordings/Grand Theft Amphibian/2021-03-27 02-21-47.mp4
6.  

It's nice that Unity detected an infinite loop. That could, of course be catastrophic. However, how many times did that loop happen before deciding it was infinite? Could that possibly be a source of these horrible slow downs in Unity?

 

Or maybe this... with NO third party assets and 8 of my own scripts. This now happens *every* time I save an edit to a script.

 

@Aras -- Just a suggestion. Maybe the team leads of 2020 \ 2021 should talk to the team lead of 2019 and find out what they did to keep a smooth, without "hold-on" , performance?

 

Apparently there were regressions in the editor's workflow.

https://forum.unity.com/threads/hardware-benchmarks-5800x-8400-10900f.1075852/#post-6985952

Now all that remains is to wait, and test to see if any of these problems have already been fixed

 

Hi @Aras
Thanks for the reply. I wish I could pinpoint what is causing it.

I opened up Unity and pressed CTRL+O to load a scene .. and Unity had a 1 second "hold on".
I pressed save in the prefab mode and got a 10 second "hold on" for the mouse interaction.
Editing a script in VS 2017 and going back to Unity has a "hold on " delay etc etc

I'm not complaining. Just that prior to ver 2020, nothing like this lagged the editor. This is very unusual and all these compounding "hold on" moments are a bit disruptive to workflow.

I wish I could be more descriptive on the cause, but I have no idea where the origin is since the "hold on" application.tick occurs at almost every interaction with the editor. I don't think uploading my 50GB project would be productive.