1.18.2 Unclear cause: OpenGL error that returns player to Main Menu after game freeze

[xFirefalconx]

Describe the bug
Game freezes suddenly and returns you to main menu. Debug window gets spammed with OpenGL errors with high severity.

To Reproduce
Steps to reproduce the behavior: (this is not guaranteed to work! it happens randomly (it seems))

1. Download my Modpack "Royal Equines: Petrified Magic" and make sure both oculus and this mod are installed.
2. Enter a world. Play a bit, walk around, dig a deep hole, interact with monsters, try to pick up XP, or monster loot, I have no clue.
3. Sometime between entering and now your game might freeze, a few seconds at least. Stop giving any input or it'll crash. Just sit and wait.
4. Game will respond again but show the dirt screen with a message like "Server closed" - huh we're in singleplayer??
5. You return to main menu. Likely, you can restart the world and move on.

The time I experienced the bug was when digging a hole with a pickaxe into stone, standing around idly.
The other time, I defeated a trumpet skeleton (I added the mod a few minutes before the second crash, fresh game start) and it dropped nothing and I also didn't see XP orbs. I walked around, turned a little and the error froze my game.

Expected behavior
No freeze, no throwing player back to menu.

Screenshots
N/A

Additional context
Add any other context about the problem here.

Render thread
OpenGL debug message: id=1282, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_OPERATION error generated. Wrong component type or count.'

latest.log

[max-widmaier]

This likely isn't an issue with mod. From the fact you need an occulus, you're probably playing in VR, right?
I'm going to try to explain this as this is definitely an odd bug. First and foremost, the "Server Closed" message can actually happen in singleplayer (it shouldn't but it can happen). You get this message because technically, a singleplayer world is just a private server. That's also why you can so easily open it up to LAN.

As for the OpenGL error and crash, this is definitely not good. OpenGL is a package of software used to render programs and video games using the GPU. So when there's an OpenGL error, that means the actual graphics rendering has messed up. This makes me think that it could possibly be the VR mod itself or some other mod because my mod doesn't really do any rendering stuff.

The only other possibility is that somehow my mod destabilizes the rendering which I highly doubt is happening. I hope this provides some context and helps you identify your bug!

I'll try to give you some extra tips as well. Try to look for mods that change how the game looks (for example how blocks are shown. I think one of the better examples of that one mod that makes block no longer blocks, something like that). The other option is the vr mod because that could change how rendering is done. The final possibility is that somehow, somewhere your GPU ran out of memory and just refused to do anything else.

The only thing weird is that it didn't completely crash, so it probably doesn't have to do with the GPU.

[xFirefalconx]

Thanks for your fast reply. It seems something else is going on, as I identified the same issue with an entity ticking, the OpenGL seemed to just be a console spammer in here. I don't use VR but have shader packs installed and need oculus to load them.

It's all super confusing to me. I keep looking for more details.
This is possibly now unrelated to your mod as the crash persists after disabling it, but maybe you got an idea which mod could cause that? I had the crash before without the trumpet skeleton mod so... uh, strange.

crash-2023-05-31_23.40.34-server.txt
latest.log

You can mark this as external issue if it happens to be just that, I just hope I figure out whom to send these reports now scratches head

[max-widmaier]

Looks like the OpenGL stuff is mostly just debug info. I remember a while back, I had the same issue where optifine would just spam opengl errors for no reason. It's annoying but not necessarily an issue per se, but it could also indicate there's an issue with your shaders. The actual crash is weird. The original one says it's the result of a zombie ticking which is odd. The next crash is because of the skeleton trumpet mob. That could be an actual issue, as there seems to be an issue with their mixin (technical term for code that just sort of added to existing code without actually overriding the files). However, it could be the same issue here and it just so happens it occurred to the trumpet skeleton mob.
It difficult to tell because all the stuff in the stack traces have unreadable names. (m_whateverwhatever_12345, or something like that).
My best guess is that it has to do with shaders because of the OpenGL stuff. You could try just taking out half of your mods and try to use the process of elimination.

[xFirefalconx]

Thanks for that insight.
I think I have an idea right now, it could be possible that I did something with the KubeJS settings... gotta investigate that further. I tried something and never finished the script so it could cause hiccups. If that's not it I'll probably have no choice but pluck everything apart again (must be my 7th time by now), can't be avoided then.
The Zombie info is super helpful so i will definitely keep that in mind! Thanks again. (I can keep you updated if you'd like)

[xFirefalconx]

Edit, that wasn't it, I used cats in that plugin so unrelated. I'll wait for the mod dev's reply of the doot skeleton x)