How to reproduce:

Create a new project
Set up the Perforce Version Control
Install AI Assistant
Open the Profiler (Windows > Analysis > Profiler)
Select “Edit Mode”
Create a new folder and select it
Observe “CPU Usage” in Profiler and overall responsiveness of the Editor

Actual result: “CPU Usage” is intense (up to 66ms) and the Editor becomes impractically slow
Expected result: “CPU Usage” is low (bellow 16ms) and the Editor quickly responds and updates the UI

Reproducible with: 1.5.0-pre.1 (6000.3.16f1, 6000.4.9f1), 2.9.0-pre.2 (6000.0.76f1, 6000.3.16f1, 6000.4.9f1, 6000.5.0b10, 6000.6.0a4)
Not reproducible with: 1.0.0-pre.12 (6000.3.16f1, 6000.4.9f1), 2.9.0-pre.2 (6000.6.0a6)
Could not test with: 1.5.0-pre.1 (6000.0.76f1) (AI Assistant not available)
Fixed in: 2.9.0-pre.2 (6000.6.0a5)

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:

It is not necessary to connect the project to Cloud in order to reproduce
The issue disappears when enabling “Work Offline” under Version Control settings (Edit > Project Settings > Version Control)
The Console is filled with following errors when recording with Profiler in some versions:
- Missing Profiler.EndSample (Every BeginSample call must have a subsequent EndSample call within the same frame): ProfilerWindow.Render
- IndexOutOfRangeException: Index was outside the bounds of the array.
  UnityEditor.IMGUI.Controls.MultiColumnHeaderState
- GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced.
  UnityEngine.GUIUtility:ProcessEvent (UnityEngine.EntityId,intptr,bool&)