Steps to reproduce:
1. Open the attached user's project "ThreeOne.zip"
2. Open the Profiler window and set it to Edit Mode
3. In the "CPU Usage" list, only highlight "Others", to make the spikes more noticeable
4. Wait for approximately 2 minutes or move around in the Scene View
5. Profiling the lag spikes show its cause as EditorLoop > Application.Tick > CheckLicensingClientNotification
6. Select CheckLicensingClientNotification to highlight further spikes
7. Wait
8. Spikes get bigger and bigger, CheckLicensingClientNotification takes more and more time
Expected results: CheckLicensingClientNotification increases overtime when profiling the Editor
Actual Results: CheckLicensingClientNotification does not increase over time when profiling the Editor
Reproducible in: 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Could not test on 2020.3.48f1 due to the project silently crashing with no stack trace
Reproducible on these environments:
Windows 11 Home 22H2 (Version: 10.0.22621 Build 22621.1555)
Not reproducible on these environments:
Windows 10 Enterprise (Version 10.0.19045 Build 19045)
Notes:
-User has noted that: "While waiting, I tend to do non-destructive actions to pass time: moving the mouse cursor, clicking on things, moving editor tabs and windows... this makes me feel like the spikes appear earlier. These actions seem inconsequential but I am noting them in case they're not. I have been able to repro without ever starting playmode or editing any serialized file in the Project"
-This does not reproduce on a new project, only reproduces on the project provided by the user
-On 2022.2.19f1 the increase is less noticeable if the editor is left idle, however it starts increasing from ~20ms to ~30-40ms if Scene View is being navigated and left to idle after
-User has noted that the performance degradation becomes more noticeable after an hour of working with the Editor