"MOJANG" Loading Screen Stuck at 100%

[unilock]

Hello Forge Forums! I'm new here, so let me know if I got anything wrong.

I'm trying to load Minecraft using a large amount of Forge mods. (489 JARs worth, apparently)
However, upon launching the game, the "MOJANG" loading screen eventually stops updating after the loading bar reaches 100%.
I left the game running for at least 30 minutes with no change.

The log loops

[Thread-0/WARN] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Configuration file /Users/unilock/Library/Application Support/PrismLauncher/instances/UNIPACK/.minecraft/config/washingcauldron-common.toml is not correct. Correcting
[Thread-0/DEBUG] [net.minecraftforge.common.ForgeConfigSpec$Builder$1/CORE]: List on key IgnoreWords is deemed to need correction. It failed validation.
[Thread-0/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file washingcauldron-common.toml changed, sending notifies
[Thread-0/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file ../reauth.toml changed, sending notifies
[Thread-0/WARN] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Configuration file /Users/unilock/Library/Application Support/PrismLauncher/instances/UNIPACK/.minecraft/config/agricraft/config-client.toml is not correct. Correcting
[Thread-0/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file agricraft/config-client.toml changed, sending notifies

after

[net.minecraft.client.renderer.texture.TextureAtlas/]: Created: 8192x8192x4 minecraft:textures/atlas/blocks.png-atlas

until the "java" process is killed.

debug.log: https://gist.github.com/unilock/e600dd47c88f56a5da8fce1634406003
(careful, it's 56344 lines long!)

Info:
- CPU / GPU: Apple M2
- OS: macOS Ventura 13.1
- Java version: "OpenJDK Runtime Environment Zulu17.38+21-CA (build 17.0.5+8-LTS)"
- Launcher: Prism Launcher v6.1
- Minecraft version: 1.18.2
- Forge version: 40.2.0

Note that the only mod config change I've made is disabling AgriCraft's Create compat (`./config/agricraft/config-client.toml":"Compat"."Enable Create compat"."Enable Create compat" = false`) in order to fix a known issue in AgriCraft that causes a crash while loading the game.

Any help would be much appreciated
 

Edited January 12, 2023 by unilock
minor edits

[warjort]

The last thing in that log is

Quote

[12Jan2023 05:49:52.479] [Thread-0/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file agricraft/config-client.toml changed, sending notifies

Which suggests an issue with agricraft.

Try removing agricraft altogether and see if you still have the problem.

Backup your world before removing mods.

 

Another reason why you can a stall in the loading screen is because you don't have enough memory assigned to the java process.

Java goes to 100% cpu utilization trying to find free memory where little exists. If this is happening, tt will eventually either finish or crash with an "out of memory" error.

[unilock]

55 minutes ago, warjort said:

The last thing in that log is

...

Which suggests an issue with agricraft.

Try removing agricraft altogether and see if you still have the problem.

The three config file warnings at the end of the debug log reference Agricraft, ReAuth, and Washing Cauldron, so I suppose I'll remove all three for the sake of testing. (as well as AgriCraft Optifine Compat, a mod that fixes AgriCraft conflicts with shaders, and InfinityLib, which is just an AgriCraft dependency. note that I do not use OptiFine!)

 

55 minutes ago, warjort said:

Another reason why you can a stall in the loading screen is because you don't have enough memory assigned to the java process.

Java goes to 100% cpu utilization trying to find free memory where little exists. If this is happening, it will eventually either finish or crash with an "out of memory" error.

I had 8 GiB (8192 MiB) of RAM allocated, but I'll try 12 GiB (12288 MiB).

 

55 minutes ago, warjort said:

Backup your world before removing mods.

I haven't been able to get the game to start at all yet :v
(well, I did once, but I honestly have no idea what I did that fixed it, nor what once again broke it...)

 

UPDATE:
Now the log stops entirely after

```
[Render thread/INFO] [net.minecraft.client.renderer.texture.TextureAtlas/]: Created: 8192x8192x4 minecraft:textures/atlas/blocks.png-atlas
```

(hm, can I not make code blocks in replies?)

EDIT: New debug.log: https://gist.github.com/unilock/c4063a805f9ce1ea7305149cf873240a

I think next I'll try removing Smooth Boot (Reloaded), a mod which makes the game's startup process multithreaded. Wish me luck.

Edited January 12, 2023 by unilock
specify Forge version of Smooth Boot

[warjort]

If you can download the java jdk (java development kit) and use the "jstack" command to get a thread dump, we can see where it is stuck.

https://www.baeldung.com/java-thread-dump

 

Otherwise you are going to have to experiment with removing mods until you find the mod that makes the problem go away.

[warjort]

Quote

[12Jan2023 07:20:23.619] [pool-3-thread-1/DEBUG] [Forgery/]: Original Mixin error org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException: Critical injection failure: @FabInject annotation on build could not find any targets matching 'method_30987()Lnet/minecraft/class_5485;' in net.minecraft.world.level.biome.BiomeGenerationSettings$Builder. Using refmap fabrication-refmap.json

You seem to have at least one fabric mod installed?

[unilock]

Removing Smooth Boot (Reloaded) fixed the issue! Thanks for the assistance!

I can still get that thread dump (with Smooth Boot installed) if you want to take a look at it. If not, could you give any tips on what to look for for what's causing the freeze? I'd like to report the bug on Smooth Boot's issue tracker.

 

1 minute ago, warjort said:

You seem to have at least one fabric mod installed?

I have the mod Forgery installed, which is a Forge port of the mod Fabrication. I guess they didn't rename their refmap 🤷‍♀️

[warjort]

You should give the thread dump to the smooth boot mod author.

[warjort]

Quote

@FabInject annotation on build could not find any targets matching 'method_30987()Lnet/minecraft/class_5485;

They didn't remap the mixins either. Or they were suppossed to remove that file?

That is a fabric "intermediary" class mapping which won't work with forge.

Edited January 12, 2023 by warjort

[unilock]

11 minutes ago, warjort said:

You should give the thread dump to the smooth boot mod author.

Will do, thanks

 

8 minutes ago, warjort said:

They didn't remap the mixins either. Or they were suppossed to remove that file?

That is a fabric "intermediary" class mapping which won't work with forge.

Now that... is above my paygrade

But I imagine it has something to do with this:
https://git.sleeping.town/unascribed/ForgeryTools#forgerytools

(referenced in Fabrication's source here)

[unilock]

 

Good news, I'm having this issue again. I had to remove Quark to get it working again, but unfortunately that's not something I can (/ want to) do this time around. Hopefully I can debug my way out of this instead?

debug.log *with* Quark (a bit after it freezes): https://gist.github.com/unilock/1e15ee76f39521271440fd2f1a84aa47#file-debug-broken-log
debug.log *without* Quark (on the title screen): https://gist.github.com/unilock/1e15ee76f39521271440fd2f1a84aa47#file-debug-working-log

Thread dump *with* Quark: https://gist.github.com/unilock/1e15ee76f39521271440fd2f1a84aa47#file-threaddump-broken-txt
Thread dump *without* Quark: https://gist.github.com/unilock/1e15ee76f39521271440fd2f1a84aa47#file-threaddump-working-txt

I *think* the freeze has something to do with the last line of the log w/ Quark installed:
```
[Render thread/INFO] [net.minecraft.client.renderer.texture.TextureAtlas/]: Created: 16384x8192x4 minecraft:textures/atlas/blocks.png-atlas
```

The log w/o Quark reads the following:
```
[Render thread/INFO] [net.minecraft.client.renderer.texture.TextureAtlas/]: Created: 8192x8192x4 minecraft:textures/atlas/blocks.png-atlas
```
...and obviously continues past that message as well.
The difference is (what I assume to be) the difference in image dimensions between the two generated `blocks.png-atlas` files(?).

Any thoughts?
 

Edited January 15, 2023 by unilock

[warjort]

The "broken" thread dump just shows it processing image data. It is not "stuck".

Of course it might be looping infinitely due to one of your mods breaking minecraft's internal data structures. But that isn't something we can diagnose with a log.

 

If you managed to narrow it down to the quark mod, I suggest you check you have the latest version then contact the mod author.

But it could also be as I said above, where the increased number of mods requires a bigger texture atlas for more textures. That is stressing your memory and the java garbage collector.

[unilock]

It worked after I removed Biomes O' Plenty, with Quark still installed. I am convinced it's because there are simply too many textures for the game to stitch together (or more likely, as you said, too many for my hardware). Which I think is pretty funny!
(I'm not a big fan of Biomes O' Plenty anyway)

Thanks for the help, again

EDIT: It should be noted that Smooth Boot (Reloaded) still stops the game from loading, even if it would otherwise (when enough mods are removed). Maybe because it runs more threads concurrently, thus making the game use more memory at once... or something.

Edited January 15, 2023 by unilock