-
Posts
6 -
Joined
-
Last visited
simonmicro's Achievements
Dirt (1/9)
0
Reputation
-
Launcher crash by minimum memory requirement, causing Minecraft not to load
simonmicro replied to simonmicro's question in Technic Launcher
Thank you very much for your response! I've noted those to my projects for when I stream next time Got speed! -
Launcher crash by minimum memory requirement, causing Minecraft not to load
simonmicro replied to simonmicro's question in Technic Launcher
Oh, good to know - is there anyone already working on this? I have to admit, that I have currently no time to take a look into that... -
Launcher crash by minimum memory requirement, causing Minecraft not to load
simonmicro replied to simonmicro's question in Technic Launcher
Hi, okay, something we are doing different... I recorded my steps to reproduce this bug - if you follow them "frame-by-frame" you should be able to trigger it. -
Launcher crash by minimum memory requirement, causing Minecraft not to load
simonmicro replied to simonmicro's question in Technic Launcher
Hi, I can trigger this also for other values, you should be able to also trigger it when you lower your allocated memory for Minecraft. Open the launcher settings and set it inside the Java section e.g. to a value of 2GB. The error should now also occur if you are requiring >2GB. -
Launcher crash by minimum memory requirement, causing Minecraft not to load
simonmicro replied to simonmicro's question in Technic Launcher
It is my own, so I've tested everything from 512MB to 256GB - every time the allocated memory for minecraft is not enough, this happens (meaning you select 1GB and the pack needs 2GB -> warning would be shown, but instead it crashes silently). -
simonmicro changed their profile photo
-
As first the relevant section of the console logs: [B#693] 2021/09/19 20:52:55 [SEVERE] java.lang.NullPointerException [B#693] 2021/09/19 20:52:55 [SEVERE] at net.technicpack.utilslib.Memory.getClosestAvailableMemory(Memory.java:73) [B#693] 2021/09/19 20:52:55 [SEVERE] at net.technicpack.launchercore.modpacks.RunData.getValidMemory(RunData.java:84) [B#693] 2021/09/19 20:52:55 [SEVERE] at net.technicpack.launcher.ui.components.FixRunDataDialog.recommendSettings(FixRunDataDialog.java:96) [B#693] 2021/09/19 20:52:55 [SEVERE] at net.technicpack.launcher.ui.components.FixRunDataDialog.<init>(FixRunDataDialog.java:52) [B#693] 2021/09/19 20:52:55 [SEVERE] at net.technicpack.launcher.launch.Installer$1.run(Installer.java:145) [B#693] 2021/09/19 20:52:55 [SEVERE] at java.base/java.lang.Thread.run(Thread.java:829) [B#693] 2021/09/19 20:54:47 [INFO] Attempting to open /home/***/.technic/logs [B#693] 2021/09/19 20:54:47 [INFO] Using file:/home/***/.technic/logs/ [B#693] 2021/09/19 20:54:47 [INFO] Intermediary path file:///home/***/.technic/logs/ This only happens, when the modpack selected specifies a minimum memory requirement, which is not fulfilled. Normally a window detailing this problem would show up, but I guess there is the problem. This bug does not happen when the memory requirement is satisfied and appears on all platforms (Windows, Linux, Mac). The launcher does not hide or react in any other way than displaying the "Play" button after pressing.