Adam James Switzer

I THINK I KNOW WHY!!!
Having the curseforge app ACTIVE while running Minecraft produced the spam!

I launched MC without curse/overwolf running. Then While in-game, I turned curse on, AND BOOM!

Just found out my friend has this spam of the logs.

Me and a friend of mine got pretty much the same issue, except that we don't have an FPS counter.

Occurring on both curse and regular launchers.

I've been looking for one like that.

now only 1.17+ is hit, and suppression helps not at all.

I've even reset my OF settings. NOPE

I wonder if it's a Java screw-up or something.

The errors MAY have stopped, but I'm gonna keep my eyes on it if the errors return and report back asap.

Error Is back. Added a new attachment to something I saw that threw red flags like the instance before I ran the instance that blew up with that Damn error. And another one before the spam error instance

This time, the 1.17.1 instance was the first with it.

Update:

I think it's been fixed as It was a JAVA error somehow causing it.

I'll keep looking out for a bit if this comes back.

Any updates?
Cause I'm still getting this error on 1.14 and Above.

Doesn't quite match. Similar, but not an exact match. Only the **OpenGL debug message, id=1280, source=API, type=ERROR, severity=HIGH, message part matches, then mine has an extra set of words before the GL_INVALID_ENUM part.
I was running Pure unmodified Vanilla 1.14 through 1.17, the latest versions of each, and while In the main menu, I saw the log spam.