Posted September 9, 20196 yr What happens: When launching Minecraft with Forge installed the game window opens up and presents the Forge loading screen where it's initializing all the game details, about half way through this process my entire computer freezes and I'm forced to reboot to regain control (UI hangs during the freeze). What I've tried: Installing Forge with the automatic installer on the latest version of Minecraft (1.14.4) with Forge version (28.0.101), THIS WORKS and Forge works fine and doesn't nuke my PC, only issue is that it's not compatible with any mods I want to install. I have tried changing the amount of memory allocated to Minecraft, tried once with 2GB of memory allocated, tried many times with 4GB allocated, tried once with 6GB allocated. I tried running Minecraft without Forge (this works) I've tried using programs such as MultiMC, atlauncher and also just manually installing Forge - nothing works. Tried using a more recent version of Java, this isn't supported by Minecraft anyway so this was really a last ditch attempt. What would probably be a good idea: Trying on another computer, although I don't have a second device with Ubuntu installed on. Finding the exact moment that the crash happens because it seems to happen at the same time during every loading of Minecraft Useful info: Minecraft version: 1.12.2 Forge version(s): 14.23.5.2846 & 14.23.5.2768 Operating System: Ubuntu 19.04 Java version: openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~19.04.1-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) Java parameters: -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M latest.log contents: https://privatebin.net/?2be9be8a779d2204#6FCj1jgcFrrssK28ggfYGpzcNRMBoV2tqMF7vqsQumsa debug.log contents: https://privatebin.net/?e65214982aba67f2#ETyHtuouwVnPv795GQd3QezgXW8vZKK3y9BgGscYF57K Edited September 9, 20196 yr by slami223
September 9, 20196 yr Author 6 hours ago, diesieben07 said: That latest.log does not look complete. Pleasepost debug.log. Added it to the bottom of the post: https://privatebin.net/?e65214982aba67f2#ETyHtuouwVnPv795GQd3QezgXW8vZKK3y9BgGscYF57K
September 9, 20196 yr Author 1 hour ago, diesieben07 said: Actually I am kinda stupid. Please try it without all those crazy GC tunining parameters. Is there any hs_err_pid files in your minecraft folder? Tried without the parameters, still crashes. There are no hs_err_pid files. 1 hour ago, diesieben07 said: That still just stops in the middle of things... Are you sure you are uploading the complete file? Yes, that was the complete file
September 13, 20196 yr Author 12 hours ago, ConnorJC said: I'd be willing to bet good money this is because you're running out of RAM. I have 8GB of ram in my computer and I've already tried setting the limit that java can use down to 2GB so I'd have a lot of leeway. I've also been able to run Forge on newer versions of Minecraft, however, this is still not good because lots of mods haven't been updated.
September 13, 20196 yr Please provide a screenshot of your .minecraft folder This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
September 14, 20196 yr Author https://privatebin.net/?4d49bfe5f0a318a6#2vayb1tTKVu6Bt2DoJSWv9WJWhmyCRM9FbpxF1JQoCqJ Launcher_log.txt (after crash) https://privatebin.net/?4243b5512b3320b2#CU13pozb9mGAC3y2E2ANqLsTMkfQWLXKvMtCfkMLHPM9 debug.log (after crash)
September 14, 20196 yr Author 3 hours ago, DaemonUmbra said: Please provide a screenshot of your .minecraft folder done
September 14, 20196 yr How long have you allowed things to stay frozen? This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
September 14, 20196 yr Author Just now, DaemonUmbra said: How long have you allowed things to stay frozen? in the past I would just leave it and go get a cup of tea, so quite a long time
September 14, 20196 yr How much ram is physically in the machine? This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
September 14, 20196 yr Author 4 minutes ago, DaemonUmbra said: How much ram is physically in the machine? as said above, I have 8GB
September 14, 20196 yr Author Is there anything else I should provide? This seems like it could be an issue with Forge.
September 15, 20196 yr Author Is this the only place I can report this bug? Perhaps a Forge contributor could take a look at the crash logs
September 16, 20196 yr Author On 9/15/2019 at 8:33 PM, diesieben07 said: I did. There is no crash happening. During normal initialization everything just stops (as if you only posted an incomplete log). No error of any kind is shown. Right, but I'm not lying to you. Something is happening in this version of Forge that doesn't happen in other versions because otherwise I would be experiencing the same issue on 1.14.4, but I'm not.
September 16, 20196 yr Have you tried going to the splash.properties in .mincraft/config and turning the enable option to false: enabled=false? I had a similar problem and doing that fixed the problem. (BTW, this fix is listed in the Rules and EAQ-Read first or be banned) Edited September 16, 20196 yr by Yonathan Yeager
September 16, 20196 yr Author 8 hours ago, Yonathan Yeager said: Have you tried going to the splash.properties in .mincraft/config and turning the enable option to false: enabled=false? I had a similar problem and doing that fixed the problem. (BTW, this fix is listed in the Rules and EAQ-Read first or be banned) Yes I did that
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.