Crash with Simple HUD Enhanced

[ninjaguardian]

Gnetum v4.5.0 added caching for Unknown Elements, but it causes a crash with Simple HUD Enhanced.

Temporary fix: Turn off Unknown Elements in the config.

Setup:

• Minecraft v1.21.11
• Gnetum v4.5.0
• Simple HUD Enhanced v4.7.5
• Fabric 0.19.3
• FAPI v0.141.5
• Java v25.0.1

Crashlog error:

java.lang.NullPointerException: Cannot invoke "java.util.ArrayList.iterator()" because "hudInfo" is null
	at knot//com.soradgaming.simplehudenhanced.hud.HUD.drawStatusElements(HUD.java:149)
	at knot//com.soradgaming.simplehudenhanced.hud.HUD.drawHud(HUD.java:88)
	at knot//com.soradgaming.simplehudenhanced.client.SimpleHudEnhancedClient.lambda$onInitializeClient$0(SimpleHudEnhancedClient.java:36)
	at knot//net.fabricmc.fabric.impl.client.rendering.hud.HudElementRegistryImpl$RootLayer.render$mixinextras$wrapped$9(HudElementRegistryImpl.java:216)
	at knot//net.fabricmc.fabric.impl.client.rendering.hud.HudElementRegistryImpl$RootLayer.mixinextras$bridge$render$mixinextras$wrapped$9$10(HudElementRegistryImpl.java)
	at knot//net.fabricmc.fabric.impl.client.rendering.hud.HudElementRegistryImpl$RootLayer.wrapMethod$dak000$gnetum$wrapRender(HudElementRegistryImpl.java:533)
	at knot//net.fabricmc.fabric.impl.client.rendering.hud.HudElementRegistryImpl$RootLayer.render(HudElementRegistryImpl.java)
	at knot//net.minecraft.class_329.wrapOperation$cfb000$fabric-rendering-v1$wrapTitleAndSubtitle(class_329.java:3662)
	at knot//net.minecraft.class_329.method_1753$mixinextras$wrapped$226(class_329.java:236)
	at knot//net.minecraft.class_329.mixinextras$bridge$method_1753$mixinextras$wrapped$226$227(class_329.java)
	at knot//net.minecraft.class_329.wrapMethod$gio000$zoomify$preventHudRender(class_329.java:11029)
	at knot//net.minecraft.class_329.method_1753$mixinextras$wrapped$228(class_329.java)
	at knot//net.minecraft.class_329.mixinextras$bridge$method_1753$mixinextras$wrapped$228$229(class_329.java)
	at knot//net.minecraft.class_329.wrapMethod$dad000$gnetum$wrapGuiRender(class_329.java:11621)
	at knot//net.minecraft.class_329.method_1753(class_329.java)
	at knot//net.minecraft.class_757.method_3192(class_757.java:522)
	at knot//net.minecraft.class_310.method_1523(class_310.java:1393)
	at knot//net.minecraft.class_310.method_1514(class_310.java:966)
	at java.base/java.lang.Thread.run(Thread.java:1474)

[decce6]

With the same setup I cannot reproduce the issue on a fresh instance. Does it require specific config for Simple HUD Enhanced?

[ninjaguardian]

It seems like it only sometimes happens.
I've been trying to see if any other mods or specific configs cause it, but the inconsistency is making it difficult.

[ninjaguardian]

After testing, I was able to reproduce the crash with just Fabric API, Gnetum, and Simple HUD Enhanced from a fresh instance.
Log: https://mclo.gs/0OgK2JN

[ninjaguardian]

Timeline.2.mp4

latest.log
crash-client.txt

[decce6]

Many thanks for the detailed video. I've added Simple HUD Enhanced to my instance but unfortunately haven't been able to reproduce the crash so far.

After examining this more closely, it doesn't seem to be actually related to the new unknown element caching in 4.5.0. According to the stacktrace, the crash occurred while rendering the titles and subtitles HUD (at knot//net.minecraft.class_329.wrapOperation$cfb000$fabric-rendering-v1$wrapTitleAndSubtitle(class_329.java:3662)). This means the caching is actually controlled by that specific element, not "Unknown Elements" (which is designed for mods that mixin into random points to render their HUDs).

I wouldn't rule out the possibility that unknown element caching contributes to this issue, but given that the crash is quite occasional, it's likely that unknown elements is not the main culprit.

What's true, though, is that unknown elements cannot be cached reliably, due to the fact they can be rendered at arbitrary points. That's why caching for unknown elements became disabled by default in version 4.5.2.

I'll keep this open and update this when I'm able to reproduce this.

[ninjaguardian]

This means the caching is actually controlled by that specific element, not "Unknown Elements"

I haven't had the crash with Unknown Elements set to off, though. When it's on, I do get it.

Or maybe I've just been getting lucky when I turn it off.

I'll test some more subtitle related things, though. Thanks for helping!

[ninjaguardian]

I tested with "Unknown Elements" and "Title and Subtitle" off, and it still crashed.