Angelica

Angelica

Mods
9.7k Downloads

Crash when rendering Draconic Armor in AE storage monitor or crafting monitor

52871299hzy opened this issue ยท 0 comments

commented

Your GTNH Discord Username

Live_learn

Mod Version

1.0.0-beta8

Java Version

Java 21

Graphics Card Vendor

Intel iGPU

Shaders

No: Go ahead and create an issue

MCPF or other features disabled by default

No: Go ahead and create an issue

Bug Report

Whenever I put a Draconic Armor piece (for example Draconic Chestplate) into a storage monitor, the game crashes instantly with a SIGSEGV. This also happens if I auto-craft a Draconic Armor piece in AE, using a crafting CPU that has a crafting monitor.

This shows up in terminal, but it isn't in the logs:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f1b15ecd6d2, pid=138983, tid=138984
#
# JRE version: OpenJDK Runtime Environment (21.0.4+7) (build 21.0.4+7)
# Java VM: OpenJDK 64-Bit Server VM (21.0.4+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libgallium-24.2.4-arch1.0.1.so+0x6cd6d2]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /run/media/bob/data/game/prismmc/instances/GT_New_Horizons_2.7.0-beta-2_Java_17-21/.minecraft/core.138983)
#
# An error report file with more information is saved as:
# /run/media/bob/data/game/prismmc/instances/GT_New_Horizons_2.7.0-beta-2_Java_17-21/.minecraft/hs_err_pid138983.log
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

fml-client-latest.log
latest.log
hs_err_pid138983.log
prism launcher exported logs

Mod List or GTNH Pack Version

GTNH 2.7.0-beta-2

Final Checklist

  • I have searched the issues and haven't found a similar issue.
  • I have read the known incompatibilities and this is not related to one of those.
  • I am running an officially released version. (Or, if I've compiled it myself I plan to fix the issue)
  • This issue is not related to a feature that is disabed by default - Shaders, MCPF, etc. [They'll be enabled when they're ready for testing]