#Craftoria keeps crashing.

108 messages · Page 1 of 1 (latest)

rich rover
#

Craftoria crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~25k lines) | hs_err_pid33692.log | CurseForge: launcher_log.txt head / tail (~62k lines) | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt | win_event1764694549836.txt

# Problematic frame:
# J 118405 c2 net.minecraft.client.renderer.OutlineBufferSource$EntityOutlineGenerator.addVertex(FFF)Lcom/mojang/blaze3d/vertex/VertexConsumer; minecraft@1.21.1 (24 bytes) @ 0x000002896f904d5e [0x000002896f904be0+0x000000000000017e]

Mod list changes on top of the modpack:

Added mods:
emiffect-neoforge-2.1.5+mc1.21.1.jar
#

playing on my own locally hosted server; issue started today

rich rover
#

nobody?

uncut tangle
#

I'm rather new to Craftoria, been playing for a few weeks, and so far have crashed more than any other pack so far. Not sure what's up and I'm typically crash free on other sizable packs

limber dagger
#

This and yous, MiisterNiick, are so far the only two reports with this specific, and unusual hard crash, in the jvm.

#

First wonder… what GPUs are you both using?

uncut tangle
#

I've got a 5080

limber dagger
#

Nvm… not the wild hare I was chasing. One’s nvidia and one’s the other.

uncut tangle
#

"the other" KEKW

limber dagger
#

I’m precoffee, sorry

#

Low brain

#

I’m wondering what else we can find common among your setups.

uncut tangle
#

No worries! Thanks for looking into this. Like I said in my post, I'm super loving the pack so hoping it's just something simple like "update this mod"

#

I'll load it back up and try playing around for a bit more and see if I crash again (hopefully not) but if I do maybe another log might be helpful to find a common denominator

limber dagger
#

I would love it to be that simple—at it may be in the end—but so far, afaik, this is an uncommon crash.
So I’m wondering what we can find in common about your setups.

#

Wild guess #2; using Overwolf (standard) version of the CF launcher?

uncut tangle
#

I remember specifically my first crash about a week ago was pressing "U" on an item to see what recipes in EMI it was used in

limber dagger
#

Yes, there was a flurry of updates before we got to another island of stability (for most)

uncut tangle
limber dagger
#

Both on latest pack version?

uncut tangle
#

1.27

#

Should I try a "reinstall latest version" and see if that helps any?

limber dagger
#

Can’t hurt.

Imma look again at both y’all’s logs in an hour when im at a computer, and not my phone.

uncut tangle
#

Appreciate it!

limber dagger
#

In the meantime… anything you were doing in game when it happened, that you can do again and get a crash reliably?

Even an artifact or other such item that can affect play/actions that don’t use it directly?

pure sierra
#

Do you both happen to have AMD cpus

uncut tangle
#

I do indeed have an AMD cpu

uncut tangle
#

but my other ones were not

pure sierra
#

This might be a gpu driver issue

#

Did you update recently?

#

You didnt get a proper crash report?

#

in ./crash-reports

#

Also mind sharing your JVM args?

#

Also are you using shaders?

#

You could try using a different java runtime (e.g., Adoptium/OpenJDK)

uncut tangle
#
  • updated semi-recently, nvidia driver 581.80 (released Nov 4)
  • don't seem to have a "crash-reports" in Craftoria folder
  • believe my arguments are default set by CurseForge? I don't recall changing them
  • Yes to shaders, complimentary with euphoria patches I think? game not launched at the moment
pure sierra
#

Mind just testing Prism Launcher for the funs?

uncut tangle
#

big fan of Prism Launcher, just have so many instances on CF already

#

Is there a semi-foolproof way to migrate my instances and saves over to Prism?

pure sierra
#

Then import in prism with cf format

rich rover
#

I've got a 7900xtx

#

I do have an amd cpu yeah

#

7950x3d

uncut tangle
#

exported from CF to Prism, launched it and was in the same dungeon, shot off a Ars light and crashed (new crash)

#

Craftoria crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~10MB & ~59k lines) | hs_err_pid10572.log | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | modlist.txt | win_event1764807191080.txt

# Problematic frame:
# J 114415 c2 com.mojang.blaze3d.vertex.BufferBuilder.addVertex(FFF)Lcom/mojang/blaze3d/vertex/VertexConsumer; minecraft@1.21.1 (71 bytes) @ 0x0000020c32dc0e5a [0x0000020c32dc0c60+0x00000000000001fa]

Mod list changes on top of the modpack:

Added mods:
emiffect-neoforge-2.1.5+mc1.21.1.jar
rich rover
#

Haven't crashed all day

uncut tangle
pure sierra
#

Waait

rich rover
#

same

pure sierra
#

Nick try disabling xaeros

rich rover
#

but it happened multiple times within like an hour to me the other day

uncut tangle
pure sierra
#

There's a keybind for the minimap

uncut tangle
#

Okay so far so good

#

I enjoy minimap but not enough to leave it on and crash lol

rich rover
#

very interesting cause for a crash

uncut tangle
#

welp

#

pressed the move like items into inventory button while having a sophisticated storage chest open

#

Craftoria crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~10MB & ~59k lines) | hs_err_pid8580.log | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | modlist.txt | win_event1764808006637.txt

# Problematic frame:
# J 138022 c2 software.bernie.geckolib.renderer.GeoRenderer.createVerticesOfQuad(Lsoftware/bernie/geckolib/cache/object/GeoQuad;Lorg/joml/Matrix4f;Lorg/joml/Vector3f;Lcom/mojang/blaze3d/vertex/VertexConsumer;III)V geckolib@4.8.2 (121 bytes) @ 0x000002188f0db518 [0x000002188f0daec0+0x0000000000000658]

Mod list changes on top of the modpack:

Added mods:
emiffect-neoforge-2.1.5+mc1.21.1.jar
pure sierra
#

My guess are drivers but I'm not sure

uncut tangle
#

Yeah all good, apprecaite you looking into it

pure sierra
#

@kindred owl Might be able to read further into the log

limber dagger
#

I was gonna guess Traben's EMF; bit wild guess, but it's the more recent pack change, than Embeddium or Iris, the other mods in the stack trace in both players' hs_err files.

rich rover
#

interesting idea

limber dagger
#

-# just throwin' that out; Lingaurdium is the better bet.

kindred owl
#

yeah, my guess is also drivers not liking the shaders.

#

same issue someone else has had with shaders with a NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 GL version 4.6.0 NVIDIA 581.80, NVIDIA Corporation and disabling shaders fixed it (or using complimentary shaders, but you seem to be using those already)

rich rover
#

I'm on an AMD GPU and got the same error

limber dagger
#

Aside, Ling, I guess the differences in the text for the crash frame comes down to the two different OpenJDK distros these two players are using?
-# (It's the same crash, right?)
# J 118405 c2 net.minecraft.client.renderer.OutlineBufferSource$EntityOutlineGenerator.addVertex(FFF)Lcom/mojang/blaze3d/vertex/VertexConsumer; [email protected] (24 bytes) @ 0x000002896f904d5e [0x000002896f904be0+0x000000000000017e]
vs.
# J 152255 c2 com.mojang.blaze3d.vertex.BufferBuilder.addVertex(FFF)Lcom/mojang/blaze3d/vertex/VertexConsumer; [email protected] (71 bytes) @ 0x000001bfe768015a [0x000001bfe767ff60+0x00000000000001fa]

kindred owl
#

could just be a difference in what is adding a vertex to a buffer

rich rover
#

completely unrelated question but im in the citidel from Iron's spells, how do I summon what I assume is supposed to be a boss in this big arena room?

#

See something called a Cinderous soul rune

#

OH

limber dagger
#

Better a question for #craftoria channel; more players there.

#

-# about the Citadel boss

rich rover
#

I think i figured it out

limber dagger
#

i did not.

#

-# i have only recently even touched it; but not for error log analysis.

pure sierra
#

It said just that

#

Hence me asking

rich rover
#

impressive

limber dagger
#

Then it must be a genius, that chatgpt. ^^

pure sierra
#

But yeah I'd try playing around with the drivers

#

Just to start somewhere

limber dagger
kindred owl
#

-# things can be 2 things at once

limber dagger
#

Old school way to compare logs (opendiff tool on macOS... goes back to NeXT, iirc)

pure sierra
#

chatgpt aint too bad at reading logs

rich rover
#

honestly might start using chatgpt to analyze my crashlogs

limber dagger
#

The problem there is... you still need to get to a human who can figure out which mod.
Or at least be able to test out what chatgpt is saying before coming to someone else with it.
'Cause that's like, "Hey, I need help, and this random guy on the internet says X. What do you say?"
In which case, I feel like, "then why are you asking me?" xD

kindred owl
#

hate to be "that guy" but has any of the folks getting this crash tried official sodium rather than embeddium

rich rover
#

I have no idea what those are

pure sierra
#

Worth a try

#

You'd have to remove embeddium

limber dagger
#

(and Monocle)

pure sierra
#

im quite sad embeddium hasnt updated in a bit

limber dagger
#

Indeed.
Had a great new mainainer, and they were cooking an impressive redo for it.
New new maintainer, if it's who I think/recall it is, is also top notch
Let's hope they have time for it.

limber dagger
#

@uncut tangle , @rich rover could you be super-awesome and try out removing the ColorWheel mod, and see if that stops these crashes for you?
Lingaurdium found evidence that's likely the cause:
https://github.com/djefrey/Colorwheel/issues/43
-# well, ok, an interaction between ColorWheel and IF.

kindred owl
#

might be worth looking at logs for the ImFast warning also:
Some BufferAllocators were not returned to the pool. Forcibly reclaiming them to prevent a memory leak.

#

also might be worth trying disabling the flywheel backend again

uncut tangle
rich rover