LexManos

The installer shows the exact path to where it is trying to install. It even has a 'browse' button you can use to select whatever folder you want. That folder must have the launcher_profiles.json file. What launcher are you using?

What JVM arguments were you passing?

Start a session and e-mail me the details at [email protected] and i'll connect [Edit] Alright did some debugging with him, seems as if it's a driver issue {his graphics card/drivers is ~4 years old -.-} and the new loading screen. However the issue is NOT happening inside of Minecraft AT ALL. it's completely exiting the MC codebase and EVERYTHING java related and stalling in native code after everything else is terminated. Below is his log and driver info so I can pass it along to fry when he gets back. For now the solution is to disable the loading screen and hope nothing pokes the launcher to be stupid. [22:29:46] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker [22:29:46] [main/INFO] [FML]: Forge Mod Loader version 8.99.124.1450 for Minecraft 1.8 loading [22:29:46] [main/INFO] [FML]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_25, running on Windows 7:amd64:6.1, installed at C:\Pontus\Minecraft\runtime\jre-x64\1.8.0_25 [22:29:46] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [22:29:46] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [22:29:47] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557 [22:29:47] [main/INFO] [FML]: Found valid fingerprint for Minecraft. Certificate fingerprint cd99959656f753dc28d863b46769f7f8fbaefcfc [22:29:47] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [22:29:47] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLDeobfTweaker [22:29:48] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.TerminalTweaker [22:29:48] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.TerminalTweaker [22:29:48] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.client.main.Main} [22:29:48] [Client thread/INFO]: Setting user: zimosis [22:29:50] [Client thread/INFO]: LWJGL Version: 2.9.1 [22:29:50] [Client thread/INFO] [sTDOUT]: [net.minecraftforge.fml.client.SplashProgress:start:235]: ---- Minecraft Crash Report ---- // I just don't know what went wrong Time: 2015-08-05 22:29 Description: Loading screen debug info This is just a prompt for computer specs to be printed. THIS IS NOT A ERROR A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- System Details -- Details: Minecraft Version: 1.8 Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 84456864 bytes (80 MB) / 255066112 bytes (243 MB) up to 1060372480 bytes (1011 MB) JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: Loaded coremods (and transformers): GL info: ' Vendor: 'ATI Technologies Inc.' Version: '4.2.11762 Compatibility Profile Context' Renderer: 'AMD Radeon HD 7900 Series' [22:29:50] [Client thread/INFO] [MinecraftForge]: Attempting early MinecraftForge initialization [22:29:50] [Client thread/INFO] [FML]: MinecraftForge v11.14.3.1450 Initialized [22:29:50] [Client thread/INFO] [FML]: Replaced 204 ore recipies [22:29:50] [Client thread/INFO] [MinecraftForge]: Completed early MinecraftForge initialization [22:29:50] [Client thread/INFO] [FML]: Found 0 mods from the command line. Injecting into mod discoverer [22:29:50] [Client thread/INFO] [FML]: Searching C:\Users\Pontus\AppData\Roaming\.minecraft\mods for mods [22:29:51] [Client thread/INFO] [FML]: Forge Mod Loader has identified 3 mods to load [22:29:51] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge] at CLIENT [22:29:51] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge] at SERVER [22:29:51] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge [22:29:52] [Client thread/INFO] [FML]: Processing ObjectHolder annotations [22:29:52] [Client thread/INFO] [FML]: Found 384 ObjectHolder annotations [22:29:52] [Client thread/INFO] [FML]: Identifying ItemStackHolder annotations [22:29:52] [Client thread/INFO] [FML]: Found 0 ItemStackHolder annotations [22:29:52] [Client thread/INFO] [FML]: Configured a dormant chunk cache size of 0 [22:29:52] [Client thread/INFO] [FML]: Applying holder lookups [22:29:52] [Client thread/INFO] [FML]: Holder lookups applied [22:29:52] [Client thread/INFO] [FML]: Injecting itemstacks [22:29:52] [Client thread/INFO] [FML]: Itemstack injection complete [22:29:52] [sound Library Loader/INFO]: Starting up SoundSystem... [22:29:52] [Thread-9/INFO]: Initializing LWJGL OpenAL [22:29:52] [Thread-9/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) [22:29:52] [Thread-9/INFO]: OpenAL initialized. [22:29:52] [sound Library Loader/INFO]: Sound engine started [22:29:53] [Client thread/INFO]: Created: 512x512 textures-atlas [22:29:54] [Client thread/INFO] [FML]: Injecting itemstacks [22:29:54] [Client thread/INFO] [FML]: Itemstack injection complete [22:29:54] [Client thread/INFO] [FML]: Forge Mod Loader has successfully loaded 3 mods [22:29:54] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge [22:29:54] [Client thread/INFO]: SoundSystem shutting down... [22:29:54] [Client thread/WARN]: Author: Paul Lamb, www.paulscode.com [22:29:54] [sound Library Loader/INFO]: Starting up SoundSystem... [22:29:54] [Thread-11/INFO]: Initializing LWJGL OpenAL [22:29:54] [Thread-11/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) [22:29:54] [Thread-11/INFO]: OpenAL initialized. [22:29:54] [sound Library Loader/INFO]: Sound engine started [22:29:55] [Client thread/INFO]: Created: 512x512 textures-atlas [22:29:55] [Client thread/ERROR]: ########## GL ERROR ########## [22:29:55] [Client thread/ERROR]: @ Post startup [22:29:55] [Client thread/ERROR]: 1286: Invalid framebuffer operation

Those snapshots show the memory allocation and the jvm termination. But you haven't recorded the thread stack states or anything like that. There shouldn't be any reason for your JVM to not terminate. If you're willing i'd like to try and actively debug this on your computer through teamviewer. It's been 'reported' a handful of times before but nobody is willing to help debug it so I chalk it up to something broken on their end because we have millions of users not reporting anything.

Why?

Then something you have installed is keeping the jvm alive. Be it a poorly configured JVM, and antivirus, a mod, or something of the sort. However Forge should not be the cause of this as we'd of seen it on millions of other users. As it sounds like you have no idea what you're doing, I'll ask you this. Do you know what teamviewer is, and if so would you be willing to let me remote control your computer so that you can show me this and we can do some debugging. I highly doubt it's forge but there is nothing we can do without ACTUAL data.

That log doesnt have any errors in it. Is this message one you're seeing on the client? If so post the client logs as this is the server logs you posted and they don't have anything besides a normal connection {and a shutdown shortly after but it looks like a normal test}

User was banned for 3 days for not following the rules, Missing logs.

Forge does no such thing. It SHOULD actually increase your 'fps' {which is actually a dumb thing to use as a metric} unless you have a really really shitty computer. In which case adding mods in general would be a bad idea. And seince you've not followed the rules we have NO FREAKIN IDEA WHAT YOU ARE TALKING ABOUT OR HOW TO HELP YOU. The rules about logs isn't arbitrary you gave us exactly ZERO information we could use to help you. Congrats on that... Come back and try again with logs and preferribly jprofiler snapshots.

And then the JVM dies because the process ends and all memory is freed. There are a few things that would eat memory while shutting down, mainly saving the world. But once the JVM is dead, the JVM is dead. If you're saying the JVM DOESN'T DIE then that is a issue. You should try and grab us a profile snapshot using jprofiler {it's in the JDK bin folder, or just google it} However just randomly saying 'MASSIVE MEMORY LEAK' with no further details besides logs spanning two differnt mc version {and thus impossible to tell the differences} that don't show ANY issues is not helpful.

Some of the coremods you have installed are broken, in respect to leaves.

I wonder what could be the problem... Reading is good you know -.-

Pretty sure, all of us launch Minecraft in the exact same way. If someone who knows what they are doing wants to debug this and find out exactly where things stop that'd be nice. We do do a fancy loading screen which you could try disabling, however either way it's your drivers who are the issue not Forge as we don't do anything that a valid driver shouldn't support.

And the effort of all the modders to update to current versions is worth wasting? Just update.

Why not just have them add a resource pack....

Sounds like lwjgl doesn't like your drivers on 64bit. This should be nothing related to Forge.

None of this would be done by Forge. Delete your .minecraft folder and start again. Also next time post logs.

You have a bad mod installed, most likely optifine base don whats erroring. Remove it from your mods folder.

FML post the FML logs -.- As for those 'annoying message's thats crap Mojang decided to put in, not us, ignore it. Just post the logs -.- ALWAYS POST THE LOGS.

Seems like either ChickenBone's mods are derping up and not closing their files correctly. Or you have something holding the JVM open. Or you have a anti-virus somewhere that is touching those files while the game is trying to load them. Kill your AV and remove ChickenBone's mods and see if it helps.

why?

Unless you have an EXTREMELY FUCKED UP graphics card, like it's going to explode in the next week this shouldn't have anything to do with that. And this is why we ALWAYS want logs so we can stop guessing and bickering over what it may be the log will tell us what it is. Using a simple pastebin/gist site should be straight forward there is a giant box, you put text in that box, you click post. It gives you a link, you give us that link...

There are plans to look into it. However, it's not a high priority. You will never see the mods like you see them in Forge today. Its A LOT of work to get things going when you have nothing that you can let the modders touch. We'll see in the future. However java is be the prime target.

That wouldnt cause this, Post your log files.