sp614x / optifine

1.8k stars 418 forks source link

[Crash] Java Edition 1.19, Optifine HD U H8 pre10, crash on game launch, computer freezes #6970

Open Kuart1ss opened 2 years ago

Kuart1ss commented 2 years ago

Description of Issue

(This problem has appeared in the OptiFine HD U H8 pre8 version. I updated Optifine today but the problem persists.) I modified Minecraft 1.19JE with OptiFine HD U H8 pre10. After the modification, the game crashed during the launch, and my computer crashed directly (the restart button on the chassis failed, so I could only long press the power button to force shutdown). This crash will occur with a high probability but not 100%, and there are a few occasions when I can enter the game.

Steps to Reproduce

  1. Install Optifine using the installer
  2. Launch Minecraft with the official launcher (In fact, after testing, the Third-party launchers can also cause problems to reproduce)
  3. The game will crash shortly after the "Minecraft" window appears, while the computer goes into the deep freeze described above

OptiFine Version

OptiFine HD U H8 pre10

Installation Method

Use the stand-alone installation tool

Log Files/Crash Reports

latest.log ErrorReport-2022-7-9_21.25.30.zip

F3 Debug Screenshot

The game CRASHES so I can't take a screenshot of the debug screen

Prior Testing

The problem no longer occurs after removing Optifine

Additional Information

This problem appears and reproduces the same as the previous article on OptiFine HD U H8 pre5, pre8, and pre10. My PC hardware is: Intel Core i7-9700K with all cores overlock to 5.1Ghz, Z390 chipset, RTX 2080-Super graphics card, 32GB DDR4 dual channel RAM Java version: Java SE Runtime Environment (18.0.1.1+2) (build 18.0.1.1+2-6)

fayer3 commented 2 years ago

maybe a java 18 issue? can you try with java 17?

sp614x commented 2 years ago

Looks like a hardware or OS problem. OptiFine shouldn't be able to cause the whole computer to lock-up. The native crash log show that the crash happens in the com.mojang.datafixers.functions.PointFreeRule class.

# JRE version: Java(TM) SE Runtime Environment (18.0.1.1+2) (build 18.0.1.1+2-6)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (18.0.1.1+2-6, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# J 5040 c2 com.mojang.datafixers.functions.PointFreeRule$OrElse.rewrite(Lcom/mojang/datafixers/types/Type;Lcom/mojang/datafixers/functions/PointFree;)Ljava/util/Optional; (41 bytes) @ 0x0000020f9a3eb51d [0x0000020f9a3eb4c0+0x000000000000005d]
#
Kuart1ss commented 2 years ago

maybe a java 18 issue? can you try with java 17?

I tried java17 but the problem remains, and I also updated to the official version of 1.19.

Kuart1ss commented 2 years ago

Looks like a hardware or OS problem. OptiFine shouldn't be able to cause the whole computer to lock-up. The native crash log show that the crash happens in the com.mojang.datafixers.functions.PointFreeRule class.

# JRE version: Java(TM) SE Runtime Environment (18.0.1.1+2) (build 18.0.1.1+2-6)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (18.0.1.1+2-6, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# J 5040 c2 com.mojang.datafixers.functions.PointFreeRule$OrElse.rewrite(Lcom/mojang/datafixers/types/Type;Lcom/mojang/datafixers/functions/PointFree;)Ljava/util/Optional; (41 bytes) @ 0x0000020f9a3eb51d [0x0000020f9a3eb4c0+0x000000000000005d]
#

I didn't find any relevant information in the windows bug report so windows doesn't seem to think that the fault is related to the system crash. I still tried turning off CPU overclocking, but the problem persists. Next I will try the graphics card driver, or try it with another windows version.

JewishBanana commented 2 years ago

Same exact problem for me, specifically with optifine when launching or running for a short time the latest release it freezes windows 10. This issue only occurs with optifine, I removed all shaders to make sure it wasn't a pack or something and still freezes PC. Strange issue it doesn't happen with optifine 1.18.