EditorLoop GUI produces MB's of garbage after updating to a10 and sinks performance

Case number: 1370097
After I updated to a10 from a7 (I am using a Windows 10 PC) I felt that the editor feels sluggish (like “Hold On” windows when flying over a scene, meaning Unity is frozen for more than 0.2 sec).
Also I observed the performance sinking slowly in Play mode despite the scene is not heavy at all, both CPU and GPU were far away from 100% load. According to the Edit Mode profiler, EditorLoop generates MB’s of garbage (was ~20kb in a7) so no wonders why everything is sluggish. The same is happening in a new URP template project.
RAM consumption is high too, looks like it’s leaking sometimes
Does anyone else gets this too?

I’ve experienced a memory leak starting with 2022.1.0a8 and also starting with 2021.2.0b13

Bug - Runaway memory usage on 2021.2.0b13 - Unity Forum

I get about 20MB/sec memory leak. Submitted case 1368345, but haven’t heard a thing for over a week.

Yep, even freshly created HDRP template project with a10 goes postal quickly in Play mode - after a minute or two it’s not playable at all.

Okay, it doesn’t leak constantly for me, only after some event, maybe starting/quiting playmode.

Thanks, so it’s probably not a problem in my PC, like drivers stuff.
Also I edited the title, so it will mention performance issues too

Hi everyone, I got a reply from Unity QA and they said that they are aware of the bug and will fix it in the next alpha (a11)
That’s the link to issue tracking (doesn’t work for me): https://issuetracker.unity3d.com/product/unity/issues/guid/1366248

I can confirm that both a10 and a11 have a regression on performance. Both Game View and general use of Scene view with the Editor. When using a09 the performance is ok (great by the way). But both a10 and a11 degrades the FPS.