#Crash with PrismMC when launching more than 1 instance with axiom installed

1 messages · Page 1 of 1 (latest)

spring hazelBOT
#

@twilit badge uploaded a log, Axiom version: 2.7.0
Environment: Windows 11, 1.20.1 & 1.20.4
Mode: N/A

Description
After about a month of attempting to figure out what was disallowing me from launching more than one instance of MC with Prism, due to a very cryptic error that was thrown, I tried selectively disabling mods as a last ditch effort, and Axiom ended up being the issue, with Axiom installed on both instances (completely separate files, the instances are in separate .minecraft folders, and I even tried using different installations of Java 17 while attempting to debug.) it appears to crash.

I then tried launching with just Axiom and FAPI on both, and the second instance crashed. With Axiom just installed on one it works, and without axiom at all it works as well.

The order in which the instances are launched does not matter, its always the 2nd instance that tries to load with axiom that ends up crashing about 1/3 of the way through initializing. The other instance loads up and works fine, with all axiom features fully functional, and other than this both instances of minecraft work perfectly alone.

Logs from each crash:
Log 1, 1.20.4 launched 2nd
Log 2, 1.20.1 launched 2nd

Steps to Reproduce:
Install PrismMC,
Create 2 instances, one for 1.20.1 & 1.20.4
Install fabric, FAPI, and Axiom on both.
Launch both instances.
The instnace launched last will crash.

  • Fabric 0.15.10 on 1.20.4

Possible Solutions:

  • Update Fabric from 0.15.10 to 0.15.11

Recommendations:

  • Update Axiom from 2.7.0 to 2.8.1
  • Update Yet Another Config Lib V3 from 3.3.2+1.20.4 to 3.4.2
#

@twilit badge uploaded a log, Axiom version: 2.7.0
Environment: Windows 11, 1.20.1 & 1.20.4
Mode: N/A

Description
After about a month of attempting to figure out what was disallowing me from launching more than one instance of MC with Prism, due to a very cryptic error that was thrown, I tried selectively disabling mods as a last ditch effort, and Axiom ended up being the issue, with Axiom installed on both instances (completely separate files, the instances are in separate .minecraft folders, and I even tried using different installations of Java 17 while attempting to debug.) it appears to crash.

I then tried launching with just Axiom and FAPI on both, and the second instance crashed. With Axiom just installed on one it works, and without axiom at all it works as well.

The order in which the instances are launched does not matter, its always the 2nd instance that tries to load with axiom that ends up crashing about 1/3 of the way through initializing. The other instance loads up and works fine, with all axiom features fully functional, and other than this both instances of minecraft work perfectly alone.

Logs from each crash:
Log 1, 1.20.4 launched 2nd
Log 2, 1.20.1 launched 2nd

Steps to Reproduce:
Install PrismMC,
Create 2 instances, one for 1.20.1 & 1.20.4
Install fabric, FAPI, and Axiom on both.
Launch both instances.
The instnace launched last will crash.

  • Fabric 0.15.6 on 1.20.1

Possible Solutions:

  • Update Fabric from 0.15.6 to 0.15.11
#

@twilit badge uploaded a log, updating did nothing

  • Fabric 0.15.11 on 1.20.1
twilit badge
#

still crashes with latest version of axiom, fabric, and FAPI

#

snippet of the error for easy access:

#

this is after updating^

#

Can also provide the logs of the instance that launches fine if needed, or anything else, just lmk!

#

Please ping on reply btw!

willow belfry
#

same for me

carmine pebble
twilit badge
#

2.8.1?

#

I attached another log with trying it with all the latest mods/fabric version for 1.20.4 & 1.20.1

willow belfry
carmine pebble
#

#announcements message

carmine pebble
willow belfry
#

1.20.1 and 1.20.4

carmine pebble
#

Well 3.0.0 1.20.4 shouldn't have any lwjgl classes

willow belfry
#

first starting 1.20.1 then 1.20.4 and reverse

carmine pebble
#

Send the crash for 3.0.0 1.20.4

spring hazelBOT
#

@twilit badge uploaded a log,

  • Fabric 0.15.11 on 1.20.1
twilit badge
#

3.0.0 ^

willow belfry
carmine pebble
#

Anyways this is basically caused by a wrong launcher config

spring hazelBOT
#

@twilit badge uploaded a log, 1.20.4 3.0.0

  • Fabric 0.15.11 on 1.20.4
carmine pebble
#

Someone else fixed it by changing something in prism but I can't remember what

#

Does it even work without axiom?

twilit badge
#

yep

#

both instances work fine without axiom, and if only 1 has axiom they both work fine

#

its only when you launch 2 instances both with axiom this happens

carmine pebble
#

Well that's stupid

#

Don't launch two instances at the same time

#

Your launcher even warns you not to do that

twilit badge
#

it doesnt... the default launcher for mc just warns to not join the same world/server, thats the entire reason i use prism, to have separate instances with separate mods/configs/worlds, and it works completely fine otherwise as well, im referencing large scale redstone builds from a 1.20.1 sp world, to use pieces of that in a 1.20.4 server

carmine pebble
#

Does it happen with two 1.20.4 instances or does one have to be 1.20.1

spring hazelBOT
#

@willow belfry uploaded a log, my log :)

  • Fabric 0.15.9 on 1.20.4

Possible Solutions:

  • Update Fabric from 0.15.9 to 0.15.11

Recommendations:

  • Update Fabric API from 0.96.11+1.20.4 to 0.97.0
willow belfry
#

sorry for wasting your time. two 1.20.4 instances work fine.
just the 1.20.1 and 1.20.4 combo causes problems

carmine pebble
#

Its so obscure it's not worth fixing

#

Just some lwjgl jank

willow belfry
#

yeah

twilit badge
#

the only two versions i play on 😭

willow belfry
#

i mean "upgrading" to 1.20.4 doesnt hurt ig

twilit badge
carmine pebble
#

Its just unfortunate that 1.20.1's lwjgl is ever so slightly out of date

twilit badge
#

o wait ur in tmc

willow belfry
twilit badge
#

but yeah the 1.20.2 changes make it not worth for me atm, the only reason i have 1.20.4 is bc i joined a server using that version

willow belfry
carmine pebble
willow belfry
#

could you give feedback so i can mark them as not possible

#

in the thread

twilit badge
carmine pebble
#

I'm a bit busy but sure, in a while