Malilib/Litematica crash issue and weird hand model at bottom of screen.

[northernpike1]

I pinpointed this issue to the litematica mods with malilib included but I couldn't tell which one was actually causing this issue. I updated java to the latest version and that didn't seem to solve anything. I thought that the 1.19.2 versions of malilib & litematica I had installed were just faulty so I updated to 1.19.3 and asked my friend to update his server and that solved nothing.

The symptoms of this issue were:

• Crashing upon loading of any world
• If the game didn't crash, it would jumble my inventory into this one cube that almost looks like the player hand model but with inventory items on it. There are also little glitches on my screen that look like if someone took a knife and stabbed the screen. Unfortunately I cannot obtain a screenshot of this at present time because the game won't let me in even once.

Once again, I checked all my other mods and clients and they did not suffer from this issue unless litematica/malilib were installed. I attempted reinstallations of minecraft and that didn't solve anything, I installing fabric and the api again but nope that didn't solve anything either.

I will also be submitting a bug report to https://github.com/microsoft/openjdk/issues.

Crash report below:

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd1a51c3bc, pid=29956, tid=31340

JRE version: OpenJDK Runtime Environment Microsoft-32931 (17.0.3+7) (build 17.0.3+7-LTS)

Java VM: OpenJDK 64-Bit Server VM Microsoft-32931 (17.0.3+7-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

Problematic frame:

C [atio6axx.dll+0x1f9c3bc]

No core dump will be written. Minidumps are not enabled by default on client versions of Windows

If you would like to submit a bug report, please visit:

https://github.com/microsoft/openjdk/issues

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

--------------- S U M M A R Y ------------

Command Line: -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Dos.name=Windows 10 -Dos.version=10.0 -Xss1M -Djava.library.path=C:\Users\natbr\AppData\Roaming.minecraft\bin\b51d203551e006cb6f07281f0653579d9bf6955e -Dminecraft.launcher.brand=minecraft-launcher -Dminecraft.launcher.version=2.3.549 -DFabricMcEmu= net.minecraft.client.main.Main -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -Dlog4j.configurationFile=C:\Users\natbr\AppData\Roaming.minecraft\assets\log_configs\client-1.12.xml net.fabricmc.loader.impl.launch.knot.KnotClient --username doctordank99 --version fabric-loader-0.14.12-1.19.3 --gameDir C:\Users\natbr\AppData\Roaming.minecraft --assetsDir C:\Users\natbr\AppData\Roaming.minecraft\assets --assetIndex 2 --uuid 30896a1e11ab4f31906b42c9985cfa6f --clientId M2E3ZWZkZTMtOGMwNC00NTgwLWE3ZTItMzk5NDg2NDZmM2Rm --xuid 2535464868947187 --userType msa --versionType release

Host: AMD Ryzen 7 3700X 8-Core Processor , 16 cores, 15G, Windows 10 , 64 bit Build 19041 (10.0.19041.2364)
Time: Fri Dec 23 12:31:35 2022 Eastern Standard Time elapsed time: 395.690111 seconds (0d 0h 6m 35s)

[rycbar0]

is this a other #601?

[maruohon]

Since it's for AMD, it's more like #576. There is a fixed build for 1.19.2 in the comments of #601, but since you already updated to 1.19.3, you'll have to wait until I upload a fixed build for that to CurseForge as well.

I'll do new builds for 1.19.0, 1.19.2 and 1.19.3 for now although this issue basically affects all versions starting from 1.12.2, but it's more noticeable on large render distance and the higher terrain in 1.17+/1.18+. I guess I could also do a 1.18.2 build as well. The older versions will get the fix later via the 1.12.2 code base.

[northernpike1]

is this a other #601?

id say its somewhat different esp with the weird hand model

[maruohon]

Try the latest mod version released a few days ago. If you are in 1.19.3 then it would be 0.13.1.

[northernpike1]

right thanks

[maruohon]

Did that latest version fix the issue for you?