Crashes with 1.20.1 beta and other mods

[Vadewolf]

Issue Description:

Note: If this bug occurs in a modpack, please report this to the modpack author. Otherwise, delete this line and add your description here. pokecube keeps crashing my game

What happens:

that idk but every log ive seen from my side shows compile tasks failing to happen then crashes or render bugs happening then crash

What you expected to happen:

the mod to work right

Steps to reproduce:

1.idk 2.something fail or break 3.crash ...

---

Affected Versions (Do not use "latest"): Replace with a list of all mods you have in.

• Pokecube AIO:1.20.1 3.23..1b alpha
• Minecraft: 1.20.1
• Forge: 47.2.0 crash-2023-10-05_18.38.25-client.txt crash-2023-10-05_18.51.06-client.txt crash-2023-10-05_21.34.55-server.txt crash-2023-10-05_21.37.26-server.txt crash-2023-10-06_18.18.09-client.txt crash-2023-10-07_13.24.32-client.txt crash-2023-10-07_15.44.23-client.txt

latest.log pokecube.log thutcore.log hs_err_pid20456.log hs_err_pid22860.log hs_err_pid24852.log hs_err_pid28424.log hs_err_pid32960.log hs_err_pid33044.log hs_err_pid49284.log

as requested by WenXin from thutmose discord

[Vadewolf]

oh one other thing i forgot to say everytime it crashes my inventory gets duplicated 100% of the time

[Thutmose]

several of those crashes are nothing related to pokecube, one was from sodium...

[Vadewolf]

there might of been one that wasnt related to pokecube oopsy but the rest were either directly or indirectly caused by pokecube from complie errors or render crashes

[Vadewolf]

hs_err_pid19484.log 100% on pokecube not other mods

[Thutmose]

Forge discord is also flooded with identical looking reports (but blaming other mods), and they seem to claim it is related to CPU/GPU drivers or java versions

[Thutmose]

specifically they are linking this as support:

https://forums.minecraftforge.net/topic/125488-rules-and-frequently-asked-questions-faq/#:~:text=How%20do%20I%20update%20my%20drivers%3F

[Vadewolf]

except all my drivers and video drivers are updated so and this issue only happens when i add in pokecube js

[WenXin20]

hs_err_pid19484.log 100% on pokecube not other mods

The log you sent says you are still using java 17.0.8, which has issues

[Vadewolf]

then CF breaks things very badly cause both u and thutmose know full well i changed that to 17.0.3 b4

[Vadewolf]

in fact according to CF this is wat im using not 17.0.8

[Vadewolf]

just had an actual mod crash this time instead of the memory crash tho b4 i did i noticed the pokemon were legit breeding so fast that within 5 minutes i had atleast 4 ratataa eggs from wild rattaa crash-2023-10-17_09.16.32-server.txt

[Thutmose]

that crash I can look into, though note, it still loaded 17.0.8, as that is what is in your crash report, check what it has in the actual minecraft launcher that curseforge brings up?

[Vadewolf]

the actual launcher itself is set to use wat ever default java MC loads with and idk how to change that

[WenXin20]

Go to installations, then edit, then more options, and then change your java version

[Vadewolf]

did that and now my world i used as a backup wont even load

[WenXin20]

then send the latest.log again...

[Vadewolf]

latest.log

as requested tho i removed pokecube and my main save loaded fine

[WenXin20]

if pokecube was removed the log isn't going to help. There's no errors or crashes in that... And that log still says 17.0.8 is being used

[Vadewolf]

ok i legit dont know how to fix that cause i changed it to 17.0.3 o n both the MC launcher and CF app

ok nvm seems the minecraft launcher resets back to default so

[Vadewolf]

ok so just found out there is no way to force change the java version in the MC launcher cause once u change it if u close out of it then it 100% resets back to default even with clicking the save button

[Vadewolf]

hs_err_pid12148.log another memory crash and its gonna say im on 17.0.8 but ive tried to change to 17.0.3 and it resets so

also i will say this latest version lasted the longest b4 crashing so yea most of the pokecube bugs did get fixed but not all of them causing the memory error

[Thutmose]

try using these arguments for JVM: -Xmx4G -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

[Thutmose]

Further testing seems to strongly indicate that this is fixed if you change to java 17.0.3 from 17.0.8

[Vadewolf]

ive tried to switch to 17.0.3 in the MC launcher it wont keep and resets itself so unless u have any idea how that cant work which sucks but i will try the jvm args