Jump to content

Server Causes Client to Crash


zSubZer0

Recommended Posts

Hello, I've been a long time Forge user (since 1.7.10) and I have done countless installations and too many hours of debugging and modded server hosting. I have been able to host a server vanilla for 1.14.4 and launch client side easily, however when I try to boot with a modded server (1.14.4 latest) and with forge client (1.14.4 latest, also tried one version from latest and an older, obsolete version (2.0.93)), Minecraft would simply crash with no error, no crash logs. I haven't checked latest but I know they've made the logs less chatty, and it's a pain to debug everything since 1.13+. Is this a known issue, or is it a new one? 


How to recreate:

Create modded server, latest 1.14.4, run

Launch minecraft with forge latest 1.14.4

 

Config folder: Did a full reboot after it crashed, clean.

Mods folder, both server and client: Empty.

RAM into server: 4-6GB

RAM into client: 6GB

RAM total: 16GB

VRAM Available: ~7GB (1070ti 8GB)

Ethernet Connection, stable

Tried a restart, no fix.

 

Note: I did manage to run both the server and the client independently, so this isn't an issue where the client is glitched and cannot startup on its own. My theory is that java is being used to run the same executable twice and cannot do that since it's trying to launch the server files from the minecraft startup process.

Edited by zSubZer0
Link to comment
Share on other sites

Yes I know, here let me post (logs aren't chatty is what I was trying to say):

 

[06Oct2019 10:02:13.024] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [--username, zSubZer0, --version, 1.14.4-forge-28.1.38, --gameDir, C:\Users\Rocco\AppData\Roaming\.minecraft, --assetsDir, C:\Users\Rocco\AppData\Roaming\.minecraft\assets, --assetIndex, 1.14, --uuid, 9d5b8b0cf2e04167aa7ce8d07d516701, --accessToken, ????????, --userType, mojang, --versionType, release, --launchTarget, fmlclient, --fml.forgeVersion, 28.1.38, --fml.mcVersion, 1.14.4, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20190829.143755]
[06Oct2019 10:02:13.028] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 4.0.0+61+ca3b447 starting: java version 1.8.0_51 by Oracle Corporation
[06Oct2019 10:02:13.272] [main/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust
[06Oct2019 10:02:14.066] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlclient' with arguments [--version, 1.14.4-forge-28.1.38, --gameDir, C:\Users\Rocco\AppData\Roaming\.minecraft, --assetsDir, C:\Users\Rocco\AppData\Roaming\.minecraft\assets, --username, zSubZer0, --assetIndex, 1.14, --uuid, 9d5b8b0cf2e04167aa7ce8d07d516701, --accessToken, ????????, --userType, mojang, --versionType, release]
[06Oct2019 10:02:15.793] [Client thread/INFO] [net.minecraft.client.Minecraft/]: Setting user: zSubZer0

 

 

 

 

I believe this is all it gave me in terms of when I tried to launch, past few logs have all looked the same and I don't think I've tried to launch since.

Edited by zSubZer0
Link to comment
Share on other sites

That's the latest, here's debug:

 

[06Oct2019 10:28:33.367] [main/DEBUG] [net.minecraftforge.fml.loading.LanguageLoadingProvider/CORE]: Adding file:/C:/Users/Rocco%20/AppData/Roaming/.minecraft/libraries/net/minecraftforge/forge/1.14.4-28.1.39/forge-1.14.4-28.1.39-universal.jar to languageloader classloader
[06Oct2019 10:28:33.413] [main/DEBUG] [net.minecraftforge.fml.loading.LanguageLoadingProvider/CORE]: Found 2 language providers
[06Oct2019 10:28:33.414] [main/DEBUG] [net.minecraftforge.fml.loading.LanguageLoadingProvider/CORE]: Found language provider javafml, version 28.1
[06Oct2019 10:28:33.417] [main/DEBUG] [net.minecraftforge.fml.loading.LanguageLoadingProvider/CORE]: Found language provider minecraft, version 1
[06Oct2019 10:28:33.418] [main/DEBUG] [cpw.mods.modlauncher.TransformationServiceDecorator/MODLAUNCHER]: Initialized transformation service fml
[06Oct2019 10:28:33.419] [main/DEBUG] [cpw.mods.modlauncher.NameMappingServiceHandler/MODLAUNCHER]: Current naming domain is 'srg'
[06Oct2019 10:28:33.419] [main/DEBUG] [cpw.mods.modlauncher.NameMappingServiceHandler/MODLAUNCHER]: Identified name mapping providers {}
[06Oct2019 10:28:33.419] [main/DEBUG] [cpw.mods.modlauncher.TransformationServicesHandler/MODLAUNCHER]: Transformation services begin scanning
[06Oct2019 10:28:33.420] [main/DEBUG] [cpw.mods.modlauncher.TransformationServiceDecorator/MODLAUNCHER]: Beginning scan trigger - transformation service fml
[06Oct2019 10:28:33.420] [main/DEBUG] [net.minecraftforge.fml.loading.FMLServiceProvider/CORE]: Initiating mod scan
[06Oct2019 10:28:33.426] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModListHandler/CORE]: Found mod coordinates from lists: []
[06Oct2019 10:28:33.442] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModDiscoverer/CORE]: Found Mod Locators : (mods folder:null),(maven libs:null),(exploded directory:null),(minecraft:null)
[06Oct2019 10:28:33.459] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFileParser/LOADING]: Parsing mod file candidate C:\Users\Rocco\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.14.4-28.1.39\forge-1.14.4-28.1.39-universal.jar
[06Oct2019 10:28:33.487] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFile/LOADING]: Loading mod file C:\Users\Rocco\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.14.4-28.1.39\forge-1.14.4-28.1.39-universal.jar with language javafml
[06Oct2019 10:28:33.513] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFileParser/LOADING]: Found coremod fieldtomethodtransformers with Javascript path META-INF/fieldtomethodtransformers.js
[06Oct2019 10:28:33.513] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFile/LOADING]: Found coremod META-INF/fieldtomethodtransformers.js
[06Oct2019 10:28:33.513] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFileParser/LOADING]: Parsing mod file candidate C:\Users\Rocco\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.14.4-28.1.39\forge-1.14.4-28.1.39-client.jar
[06Oct2019 10:28:33.518] [main/DEBUG] [net.minecraftforge.fml.loading.moddiscovery.ModFile/LOADING]: Loading mod file C:\Users\Rocco\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.14.4-28.1.39\forge-1.14.4-28.1.39-client.jar with language minecraft
[06Oct2019 10:28:33.525] [main/DEBUG] [net.minecraftforge.fml.loading.ModSorter/LOADING]: Found 0 mandatory requirements
[06Oct2019 10:28:33.525] [main/DEBUG] [net.minecraftforge.fml.loading.ModSorter/LOADING]: Found 0 mandatory mod requirements missing
[06Oct2019 10:28:33.870] [main/DEBUG] [cpw.mods.modlauncher.TransformationServiceDecorator/MODLAUNCHER]: End scan trigger - transformation service fml
[06Oct2019 10:28:33.870] [main/DEBUG] [cpw.mods.modlauncher.TransformationServicesHandler/MODLAUNCHER]: Transformation services loading transformers
[06Oct2019 10:28:33.871] [main/DEBUG] [cpw.mods.modlauncher.TransformationServiceDecorator/MODLAUNCHER]: Initializing transformers for transformation service fml
[06Oct2019 10:28:33.871] [main/DEBUG] [net.minecraftforge.fml.loading.FMLServiceProvider/CORE]: Loading coremod transformers
[06Oct2019 10:28:33.871] [main/DEBUG] [net.minecraftforge.coremod.CoreModEngine/COREMOD]: Loading CoreMod from META-INF/fieldtomethodtransformers.js
[06Oct2019 10:28:33.998] [main/DEBUG] [net.minecraftforge.coremod.CoreModEngine/COREMOD]: CoreMod loaded successfully
[06Oct2019 10:28:34.004] [main/DEBUG] [cpw.mods.modlauncher.TransformStore/MODLAUNCHER]: Adding transformer net.minecraftforge.coremod.transformer.CoreModClassTransformer@2f7a7219 to Target : CLASS {Lnet/minecraft/potion/EffectInstance;} {} {V}
[06Oct2019 10:28:34.005] [main/DEBUG] [cpw.mods.modlauncher.TransformStore/MODLAUNCHER]: Adding transformer net.minecraftforge.coremod.transformer.CoreModClassTransformer@285d851a to Target : CLASS {Lnet/minecraft/block/FlowingFluidBlock;} {} {V}
[06Oct2019 10:28:34.005] [main/DEBUG] [cpw.mods.modlauncher.TransformStore/MODLAUNCHER]: Adding transformer net.minecraftforge.coremod.transformer.CoreModClassTransformer@314b8f2d to Target : CLASS {Lnet/minecraft/item/BucketItem;} {} {V}
[06Oct2019 10:28:34.006] [main/DEBUG] [cpw.mods.modlauncher.TransformStore/MODLAUNCHER]: Adding transformer net.minecraftforge.coremod.transformer.CoreModClassTransformer@664a9613 to Target : CLASS {Lnet/minecraft/block/StairsBlock;} {} {V}
[06Oct2019 10:28:34.006] [main/DEBUG] [cpw.mods.modlauncher.TransformStore/MODLAUNCHER]: Adding transformer net.minecraftforge.coremod.transformer.CoreModClassTransformer@5118388b to Target : CLASS {Lnet/minecraft/block/FlowerPotBlock;} {} {V}
[06Oct2019 10:28:34.006] [main/DEBUG] [cpw.mods.modlauncher.TransformationServiceDecorator/MODLAUNCHER]: Initialized transformers for transformation service fml
[06Oct2019 10:28:34.019] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlclient' with arguments [--version, 1.14.4-forge-28.1.39, --gameDir, C:\Users\Rocco\AppData\Roaming\.minecraft, --assetsDir, C:\Users\Rocco\AppData\Roaming\.minecraft\assets, --username, zSubZer0, --assetIndex, 1.14, --uuid, 9d5b8b0cf2e04167aa7ce8d07d516701, --accessToken, ????????, --userType, mojang, --versionType, release]
[06Oct2019 10:28:35.585] [Client thread/INFO] [net.minecraft.client.Minecraft/]: Setting user: zSubZer0
[06Oct2019 10:28:36.665] [Client thread/DEBUG] [net.minecraftforge.coremod.transformer.CoreModBaseTransformer/COREMOD]: Transforming net/minecraft/block/FlowingFluidBlock
[06Oct2019 10:28:36.767] [Client thread/DEBUG] [net.minecraftforge.coremod.transformer.CoreModBaseTransformer/COREMOD]: Transforming net/minecraft/block/StairsBlock
[06Oct2019 10:28:36.818] [Client thread/DEBUG] [net.minecraftforge.coremod.transformer.CoreModBaseTransformer/COREMOD]: Transforming net/minecraft/block/FlowerPotBlock

Link to comment
Share on other sites

19 minutes ago, diesieben07 said:

You're running out of RAM.

Huh. I have 16GB available and typically this isn't an issue (I have 4GB free and 6GB allocated for the launcher). I'll try launching with more RAM, and if not I've had no experience like this. Thank you!

Link to comment
Share on other sites

37 minutes ago, diesieben07 said:

The error mentions the page file being too small, which suggests you are running out of actual RAM and the OS is swapping RAM to disk.

So does this mean Minecraft is overriding the maximum amount of RAM allocated or not using its maximum? Or does this simply mean I literally don't have enough storage on my C:\

Link to comment
Share on other sites

It sounds like you're telling Minecraft to use more RAM than is available

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 comment
Share on other sites

9 minutes ago, DaemonUmbra said:

It sounds like you're telling Minecraft to use more RAM than is available

I have 16GB available. Assuming about 2-3GB are being used to run my system and 6GB are being used to run my server, I should have 7-8GB left over. I allocated 6GB, meaning I should have 4 spare GB. There is no way that I don't have 16GB connected since I built my computer and I have never come across an issue like this before (I have allocated 12GB to client and still be able to run). Something's telling me that Java is trying to bypass limits to use over 16GB when it doesn't really need to, or isn't accounting for my 16GB when it should (maybe permissions telling it that it cannot use more than x amount?). Once again never had this issue in the past.

Link to comment
Share on other sites

Do you have anything else running? Chrome is known to be a bit of a hog

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 comment
Share on other sites

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.