Editor loop at 100% (100ms+) on 2020.1.0b3, 2020.1.0b2

Anyone else having issues with the beta editor where there is a constant lag (feels around 15 FPS), and when using the profiler, the Editor loop is at 100% usage?

The profiler only shows that the overall is 100%, and no single process is responsible for it.

Note: I am using Arch Linux with i3 window manager.

I know Arch is not supported, but this issue does not exist on 2019.3.5f1, it only happens on the 2020 Beta editors. I am wondering if any other Arch users are experiencing the same thing with the latest Beta editor.

For reference, I install all my editors using the Unity Hub package on AUR: https://aur.archlinux.org/packages/unityhub/

I also attached a screenshot of what it shows in the Hierarchy of the profiler.

Edit: Tested on newest 2020.1.0b4, issue still occurs. Also, issue occurs regardless of using OpenGL or Vulkan, editor is still at 15 FPS or less.

 

For anyone else that will or might have this obscure problem in the future, here's a solution that doesn't make sense but it worked anyways:

1. Go to Edit > Preferences
2. In the general section, find "Interaction Mode" (should be at the way bottom)
3. Set the value to "Monitor Refresh Rate" (mine was set at "No throttling")

CPU was instantly freed up in the editor, and the issue does not occur anymore.

Edit: Here's a 100% way to reproduce the problem:

1. Same section in general
2. Set the value to "Not throttling" (nothing will happen)
3. Restart editor
4. When the editor re-launches, the editor will be very slow and at 100+ ms on CPU. Follow above instructions and it will fix itself

 

Hello I am experiencing the same problem but on 2019.3.9f1. The game is running and the profiler is the editor one, taking almost 100 ms. It seems that most of the time is waiting for gfx.

The suggested fix from P0150N didn't work.

 

Hi jonathans42,

It happens on any project, I was able to replicate it just from creating a new empty scene project.

However, since you did mention something about infinite repaints of windows, it might just be an arch + i3 - related issue, since those are not supported by Unity.

 

A similar thing happens to me with Arch + Sway (window manager inspired by i3).

Editor Loop is taking 1s but only if I have an editor window in another workspace, not visible to the user.

Closing the other editor window, moving it to the same workspace or moving it to another workspace, visible in a secondary screen, fixes it and brings the FPS from <10 back to 200 in my case.

 

I don't know if it's same problem but I just installed 2020.1.0b7 and get all cores fluctuating around 20% just sitting in the editor.
I don't have this problem with my 19.3b install though so I think this is something new to 2020.
If I open the Help->About and then close it, I end up with one core permanently at 100%.
Mint 19.3, 3700x

 

I ran into a similar issue today in 2020.1.0b8 where all of a sudden my project wouldn't run over 70fps. Usually it's in the hundreds of fps. Profiler showed a heavy editor loop hogging everything.Clicking Layout -> Revert Factory Settings fixed it for me.

 

Hey, have you solved this problem?

 

Hi @MartinTilo,
i have in EditorLoop time ms 25973. Every expectation complicates development. Perhaps you can suggest the reason for this expectation?

 

@P0150N Amazing, your #2 solution instantly works on my project on Unity 2020.1.5f1
Unity fellows it would be great if we could test/optimize our game performance while isolating/disabling the editor itself during profiling.

[Edited] Further it lower the CPU consumption of Unity3D in my MacOS (MBP 16 inch) from 13x% to around 50%

 

Got this too on 2020.2 beta. Nothing going on script wise, 110~ms frame time, profiler just shows "Other" as taking 99% of the time, not obvious what's going on.

 

I'm having this issue too, I'm not sure how or when it started but it makes thinks almost unusable. The suggested workaround didn't work for me. I'll try from a fresh install later this week.

 

Thanks for the detailed troubleshooting guide for now I wasn't able to get much more information from the profiler. What made me add to this thread is that I'm using Manjaro and have almost the same editor loop duration (around 100ms).
I'll just wait for my new SSD in a couple days and try on a fresh install of manjaro and if I still get the issue I'll check on Ubuntu and then make a bug report once I have more to report.

 

Issue still exists in 2020.2.0b5. I have attached a profiling result: looks like EditorLoop itself takes most of the CPU time.

I think this bug is already filed. It was marked as "Fix In Review" for some time, but currently it is marked as "Active" again.

https://issuetracker.unity3d.com/is...-play-mode-is-unable-to-reach-more-than-10fps

 

We do have a fix coming for this. It's making it's way into trunk.

 

How do I see when this is coming out or what version contains it?

I think I have the same issue on windows 10:
https://i.imgur.com/1ld94zD_d.webp?maxwidth=640&shape=thumb&fidelity=medium

 

This is fixed in 2021.1.0a4. It looks like there is a backport coming for 2020.2 as well. It should be in the next public build. Keep in mind that we normally don't backport changes for Linux. Looks like some kind soul took it on though.

 

Could we have somebody at Unity lock this thread? I feel that most of the conversations have gone off-topic with the original issue and now we just have posters chiming in with completely unrelated topics.