Crashing prevents loading into an existing world

[GameRyder]

Basic details

Are you using a legitimate launcher and Minecraft account:
yes
Are you using a computer with 8GB or more of RAM? (How to check):
yes
Are you using Java 8, 64-bit? (How to check):
yes

Information required

Is the modpack crashing: yes
Crash/latest log link (Where to find): https://mclo.gs/VIDOOv6
Is Optifine installed or any other additional mods: no

Java args: -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

Describe the issue
A clear and concise description of what the issue is.

Trying to load into an existing world causes the game to stop responding.
Once closed via task manager windows dies.
Same issue as described here.

Creating a new world works as expected.

Mipmap levels is OFF.
I tried disabling releaseSpriteFramesCache in \config\loliasm.cfg but could not find it anywhere.
No major changes to any of the settings.
Never had this issue in the past.
Reinstalled the modpack completely and still get this issue.
I've also tried loading a world with different RAM allocation values to no effect.

[xJon]

When did this issue start to happen? Did you attempt to revert back to a recent world backup?

[GameRyder]

Just yesterday when I had tried to play once again. My old worlds didn't load properly (I attributed it to different modpack version & mojang account -> microsoft account transfer).

I tried reverting to a backup to no avail. I also tried playing an older version of the game (1.4.1) where I experienced the same issue, so seems like it's something on my side.

Also unsure if this info is relevant but I am using the technic launcher.

[GameRyder]

Something else I forgot to mention:

When booting up the modpack, if I create a new world, I can re-load back into said world endlessly as long as it's the same game instance. Still cannot load other worlds.

If I close and boot the game back up I can no longer load the newly created world anymore.

[xJon]

Did this always happen to you with the modpack, or did it only recently start to happen?
Can you reproduce this issue with other 1.12.2 modpacks?

[GameRyder]

Only recently.

I cannot reproduce with other modpacks, was successful in loading an existing world in both Tekkit 2 and Vanilla.

Also tried using another launcher (CurseForge) and got same results.

[xJon]

Using CurseForge any new world stops responding once you try to enter it again?

[GameRyder]

Only after I launch a new game instance and try it stops responding. If I create a new world, exit world, and rejoin it works fine .

Once I close the game and boot it up again I can't anymore.

[xJon]

Because I'm unable to reproduce this issue and it also shows nothing in the log, I'm not sure how to efficiently further troubleshoot it from here.
You said the issue seems to be on the modpack-level, so it must be some sort of incompatibility with one or a few of the mods (I can't think of a different reason).
If you're willing to, you can cut away half of the mods in the mods folder (excluding dependency mods, e.g. !mixinbooter-5.0.jar, RenderLib-1.12.2-1.1.9.jar) and re-test, until you can find out exactly which mod/s cause the issue and that without them installed, the issue does not appear.
Actually a simpler place to start might be removing individual mods that are more likely to be the cause of the issue, especially as you mentioned it only started recently? Can you give a bit more detail in that regard?

[GameRyder]

Will do, when I have the chance I'll play around and see what I can find.

As for this only starting recently: I have played this modpack many times in the past. Never encountered any such issue. I would typically create a new world every year or every few months etc. This time around (after around a year probably of not playing) I boot up the game, update etc. When it comes to starting a world, I try booting up an existing one, doesn't work, fair enough I thought, might be really outdated. Client crashed. Computer crashed. Odd, I boot up again, try new world, it works, ... and this much I've described already.

[xJon]

So it could be one of the mods added in the last year or so of updates. Maybe try removing the loliasm-5.6.jar mod?

[GameRyder]

If that were the case then wouldn't using an old version of the modpack solve this? I tried running 1.2.2 and I get the same issue.

I feel it must be something with my PC/env but not sure what since I'm still using Java 8

[GameRyder]

Removed loliasm from latest and still failing

[xJon]

Can you double check that other 1.12.2 modpacks work correctly? Maybe Hexxit 2?
If so then it must be a mod that's preset in The 1.12.2 Pack, even in older versions as 1.2.2, but not in others. I'm not sure though.

[GameRyder]

Hexxit 2 ran with no issue, I've failed to reproduce this issue with other modpacks so far.

[xJon]

Can you do one last try with a modpack containing some more similar mods to The 1.12.2 Pack, such as The Classic Pack?

[GameRyder]

Still cannot reproduce. The Classic Pack works fine.

[GameRyder]

In a last ditch effort I uninstalled/deleted every instance of minecraft, vanilla, modded, even dungeons to get rid of the launchers.

After clearing my PC of anything MC related, I reinstalled CurseForge to give it another go and once again I failed with the same bug.

[xJon]

I'm really sorry about this odd incompatibility issue. In this case, I have no other ideas beyond this:

If you're willing to, you can cut away half of the mods in the mods folder (excluding dependency mods, e.g. !mixinbooter-5.0.jar, RenderLib-1.12.2-1.1.9.jar) and re-test, until you can find out exactly which mod/s cause the issue and that without them installed, the issue does not appear.

I will also see if others have seen something like this before.

[GameRyder]

It definitely odd and something with my PC must be causing an issue since I haven't experienced this with other modpacks. That being said I have no idea what that thing might be seeing as I did a clean wipe and retried from scratch.

I'll give a go to cutting away mods and see if that has any effect :)

As for if others have seen this issue before, as mentioned initially I believe this is the same problem: #847

Not sure if you were referring to other modpack creators with that last line ^

Thanks for your help

[xJon]

Also, can you try using the latest Java 8 version with the Technic launcher?

You can see which Java version you're using here:

[xJon]

A couple of other ideas:

• Can you provide a full game log from when you start a new world (which I assume works), and then exit it? (to check for any weird errors on exit & save)
• Can you try without the mods Jon's Exclusives, Mystcraft, and all of Mystcraft's addon mods?

[GameRyder]

I tried with both the default (Oracle 1.8.0_51 64-Bit) as well as the latest.

I've also tried allocating less/more RAM as I've read sometimes too much could also be an issue.

There's also additional arguments that I've found were meant to help with this issue (it did not), I believe it helped with garbage collection but not certain.

The only weird thing I can think of that might be different to others, but don't see why, is that on my PC I have other versions of Java, but I made sure my env vars were okay and also the correct version was always selected in whatever launcher I used

[GameRyder]

A couple of other ideas:

• Can you provide a full game log from when you start a new world (which I assume works), and then exit it? (to check for any weird errors on exit & save)
• Can you try without the mods Jon's Exclusives, Mystcraft, and all of Mystcraft's addon mods?

Sure, will do so now

[GameRyder]

logs1_create_world_and_exit.zip

[GameRyder]

I noticed from the debug logs despite setting java version to latest it used the legacy version

[GameRyder]

Removed the mods & addons. Still crashed.
log2_create_world_after_fresh_install.zip
log3_crash1_before_delete.zip
log4_create_world_after_mods_removed.zip
log5_crash2_after_delete.zip

[xJon]

Similarly to before I'm unable to find anything unusual in the logs, this is typical of "freeze" crashes (when the game is not responding) that something is going wrong on a low level so it doesn't even print the issue to the log.

Disappointing regarding my couple of mod guesses. I will continue to think about it, but the most decisive way to find the mod incompatibility would be to slowly cut away mods and continually testing.
There's a reason this issue happens with The 1.12.2 Pack, and not with Tekkit 2 for example - and that's the only way I can think of for finding out what it is.

[GameRyder]

I will work on this and try to figure out what it is. I'll comment any findings.

Thanks for your help :)

[GameRyder]

Couple of things to note:

So I approached this sort of like a binary search; adding half, if it works add another half, else the problem is in the first half, etc.
Doing so I noticed pretty quickly there was an issue with a mod starting with B (started copying in order of name and came to discover this soon after).

Afterwards I copied all but the B mods, and managed to get the game running properly, with a few odd crashes here and there, but ultimately the game was able to be run.

I've currently narrowed the list of possible causes down to:

• backups
• badwithernocookiereloaded
• BiblioCraft
• Born In a Barn
• Botania

Looking into each mod quickly, I did see post that complained "Born In a Barn" doesn't play nice with Minecraft 1.12.2 and could cause issues.

While I was adding/removing mods I experienced some issues with Mystcraft creating new profiles. Whenever I altered the mod list it would do this the first time, hang, and after force closing the game worked like normal, unless I had one of the three bolded mods mentioned above installed, in which case I got weird/random behaviour with the Mystcraft profiles.

After everything I fresh installed the pack, removed those 3 mods, and it still failed, I removed the other 2 mentioned above and it started to work again. I had it working when Botania & Backups were installed before the fresh install.

Because of all this I am giving up on determining the exact cause. I will now go play the game (minus those 5 mods).

Thanks again for the help, apologies for the lengthy response, and I hope this can help you/somebody in the future.

[GameRyder]

Nevermind I just opened JEI settings in my inventory and it crashed my PC LOL.

[xJon]

We need to keep track of the difference between any crashes you're experiencing - one of them is a freeze that's hard to determine its cause, others could be really simple issues that I can help you with. So I'd recommend you to first of all just try to find the mod that causes you to not enter existing worlds.

Regarding Mystcraft, you can set client.persave=true in \the-1122-pack\config\mystcraft\core.cfg to avoid the intrusive profiler while you are messing with mods.

Regarding the list you shared, maybe you can try to narrow it down more, but nevertheless if you can manage to get to a point in which you are able to reenter existing worlds, that's a win!
Beyond that, if you experience other crashes, if you're able to share a crash log link here it'd be great and I'll try to help.

[xJon]

Hey! Any update on this?

[GameRyder]

Hey!

I gave up on trying to narrow down the problem, I will however share an odd experience I had.

I ended up playing on a server with friends (one of us would host and we used hamachi). This worked as a way for me to rejoin an already created world while allowing me to close my game. Halfway into our playthrough, seemingly out of nowhere I began crashing when switching dimensions. I was the only person this happened to ever, so similar to my singleplayer issue it was unique to me.

Eventually I managed to find a reliable workaround:

1. Delete instance of 1.12.2 pack from both launchers
2. Reinstall one of the instances
3. Play as normal until I closed Minecraft
4. Repeat from step 1

Not sure if this tells you anything, but I thought I would share.

[xJon]

That is really weird regarding your singleplayer experience. About the dimension switching crashes, they could be due to a different reason altogether and if you can share them here I could take a look.

[xJon]

A lot of mods were updated in version 1.5.3 of the modpack. Tiny chance that helped your issue.

[xJon]

Closed due to inactivity, will reopen if requested.