Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

(Solved) Forge Crashes after FML Early Loading Process


Recommended Posts

My forge client crashes after the FML Early Loading Process finishes. I have reinstalled forge, minecraft, and before doing both of those removed all mods to see if those were the problems. Nothing seems to be fixing and I just got into a modded server with friends the other day so It's very frustrating. :(

Here's the crash report if that helps
 

Spoiler

---- Minecraft Crash Report ----
// Daisy, daisy...

Time: 5/22/20 12:04 AM
Description: Initializing game

java.lang.IllegalStateException: GLFW error before init: [0x10008]Win32: Failed to create interface
    at com.mojang.blaze3d.platform.GLX.lambda$initGlfw$1(GLX.java:245) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at com.mojang.blaze3d.platform.GLX$$Lambda$1949/445531390.accept(Unknown Source) ~[?:?] {}
    at net.minecraft.client.MainWindow.func_211162_a(SourceFile:116) ~[?:?] {re:classloading}
    at com.mojang.blaze3d.platform.GLX.initGlfw(GLX.java:244) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:427) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:365) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at net.minecraft.client.main.Main.main(SourceFile:155) [?:?] {re:classloading}
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51] {}
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51] {}
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51] {}
    at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51] {}
    at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) [forge-1.14.4-28.2.0.jar:28.2] {}
    at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$382/1443675930.call(Unknown Source) [forge-1.14.4-28.2.0.jar:28.2] {}
    at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-4.1.0.jar:?] {}
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-4.1.0.jar:?] {}
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-4.1.0.jar:?] {}
    at cpw.mods.modlauncher.Launcher.run(Launcher.java:81) [modlauncher-4.1.0.jar:?] {}
    at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) [modlauncher-4.1.0.jar:?] {}


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Client thread
Stacktrace:
    at com.mojang.blaze3d.platform.GLX.lambda$initGlfw$1(GLX.java:245)
    at com.mojang.blaze3d.platform.GLX$$Lambda$1949/445531390.accept(Unknown Source)
    at net.minecraft.client.MainWindow.func_211162_a(SourceFile:116)
    at com.mojang.blaze3d.platform.GLX.initGlfw(GLX.java:244)
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:427)

-- Initialization --
Details:
Stacktrace:
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:365)
    at net.minecraft.client.main.Main.main(SourceFile:155)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56)
    at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$382/1443675930.call(Unknown Source)
    at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37)
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54)
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72)
    at cpw.mods.modlauncher.Launcher.run(Launcher.java:81)
    at cpw.mods.modlauncher.Launcher.main(Launcher.java:65)

-- System Details --
Details:
    Minecraft Version: 1.14.4
    Minecraft Version ID: 1.14.4
    Operating System: Windows 10 (amd64) version 10.0
    Java Version: 1.8.0_51, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 4148468672 bytes (3956 MB) / 5100273664 bytes (4864 MB) up to 5368709120 bytes (5120 MB)
    CPUs: 12
    JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx5G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
    Launched Version: 1.14.4-forge-28.2.0
    LWJGL: 3.2.2 build 10
    OpenGL: NO CONTEXT
    GL Caps: 
    Using VBOs: Yes
    Is Modded: Definitely; Client brand changed to 'forge'
    Type: Client (map_client.txt)
    Resource Packs: 
    Current Language: ~~ERROR~~ NullPointerException: null
    CPU: <unknown>

 

Edited by GL1TT3RTR1P!
Problem was solved changing title to reflect that
Link to post
Share on other sites
  • 3 months later...

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. 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
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to post
Share on other sites
  • 2 months later...
On 5/22/2020 at 9:53 AM, diesieben07 said:

Add -Dfml.earlyprogresswindow=false to the JVM args.

There is this text in my JVM arguments

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

how to i add

-Dfml.earlyprogresswindow=false

into the args aswell?

Link to post
Share on other sites
  • 2 months later...
  • 2 weeks later...
On 2/27/2021 at 7:53 PM, diesieben07 said:

Dude. You need to add the text that was given in this thread.

where is the JVM arguements though? i found one in the minecraft app (on macbook) and added the text, but that didn't change anything, infact it made forge stop working entirely

 

Link to post
Share on other sites
12 minutes ago, diesieben07 said:

Your issue is not related to this thread at all.

Forge currently does not run on M1 Macs. We need to wait for Mojang to ship an updated version of LWJGL.

ah alright fair enough. thanks for your help anyway though

Link to post
Share on other sites
  • 1 month later...
9 minutes ago, Gizzy said:

hey so im on a windows pc and i added the -Dfml.earlyprogresswindow=false like the other guy but it still doesn't work?

btw in the log it says ''Process crashed with exit code 1'' But in the launcher it says ''exit code 0'' what?

Link to post
Share on other sites
1 minute ago, Gizzy said:

btw in the log it says ''Process crashed with exit code 1'' But in the launcher it says ''exit code 0'' what?

Make your own thread and post logs.

  • Thanks 1
Link to post
Share on other sites
Guest
This topic is now closed to further replies.


×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.