The release notes says that this super annoying console spam is supposed to be gone in b13:
Well, it’s not, screenshot:
I only upgraded to b13 to get rid of this.
Please fix asap, that’s soooooooo annoying. I can’t see real errors from this nonsense spam, whatever it is.
Yeah, I get the same thing in b13… just like before. When it happens I have to restart Unity Hub to make it stop. Just closing Unity Hub with the X in the top right corner doesn’t exit Unity Hub. You either have to go to the system tray, right click the Unity Hub icon and choose “Quit Unity Hub”, or kill it via the task manager. Once you do that, you can start hub again and then Unity again… and at least in my case, 233 will be quelled (until it shows up again at some future random time).
@LeonhardP @yanickb i didn’t file a bug report for that yet. Should I do that? Not sure how long it takes then, but this is really annoying and should be fixed asap like everything 
I’m under the impression that re-opening the ticket that exists for that would suffice, yet I have no information which one it is and who to address with that
Hi,
I’ve flagged it to the devs. Submitting a bug report would still be a good idea since that will ensure it’s being properly tracked and processed in the system.
I’ve been seeing this in build logs, too.
Happening in 2022.2.0b16, seems to tick up by +2 every 5 seconds. It started before the build, continued doing it after.
Rebooting my PC has solved this “problem” 
Still happens in 2022.02.0f1
Still happens in 2022.02.1f1
Happend after this:
Working my project in 2022.02.0f1
In Unity Hub, download 2022.02.1f1. Install.
While my project is being opened, I removed 2022.02.0f1.
Working project crash after a random click in the assets 
Reopen project using new version.
Console report error.
Close project
Delete Library + obj
Reopen project
Still same error.
Create new project. Good no error.
EDIT:
ROBOOT WINDOWS solves it.