FTB hanging

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Beleriond01

New Member
Jul 29, 2019
193
0
0
Dear Fellow FTBers,

I've been following the Tech support threads quite intensively over the past few days since I've been having a consistent problem with my DW20 pack install. Since I don't, yet, seem to be getting any feedback regarding my problem I figured I'd post it in the general FTB chat as well.

Another reason for doing so is that I've noticed quite a few more people seem to be getting the same problem/error, even with different mod packs.

When I start my FTB Launcher and select the DW20 pack to play, it'll load up until I see:

Loading - Initializing Minecraft Engine (4/7)
Rendering Setup - Render Global Distance (4/9)

Screenshot: http://imageshack.com/a/img908/8144/wNaCxH.jpg

What I've tried so far:
  • Force update the pack - failed
  • Remove the .jar and .json files in <\Feed the Beast\versions\1.7.10>
  • Remove the "assets" and "libraries" folders in <:\Feed the Beast\>
  • Remove the entire <:\Feed the Beast\direwolf20_17> folder
Only when I remove the entire direwolf20_17 folder and then restart my game will it proceed to go past the bit posted above. Unfortunately, when I then close the game (via Quit Game) to restart it, it will stall on exactly the same point again.

So far, I've only been able to recreate this for my DW20 pack install, mostly since I hardly play any other packs atm.

Software installed and tried:
  • Latest FTB Launcher
  • Curse Minecraft Launcher
  • Java 7 (currently installed)
  • Java 8 (currently removed)
Perhaps anyone else can shed some light as to why this is happening of late and, most importantly, what I could do to fix it.

Cheers,
Bel*.
 
Dear Fellow FTBers,

I've been following the Tech support threads quite intensively over the past few days since I've been having a consistent problem with my DW20 pack install. Since I don't, yet, seem to be getting any feedback regarding my problem I figured I'd post it in the general FTB chat as well.

Another reason for doing so is that I've noticed quite a few more people seem to be getting the same problem/error, even with different mod packs.

When I start my FTB Launcher and select the DW20 pack to play, it'll load up until I see:

Loading - Initializing Minecraft Engine (4/7)
Rendering Setup - Render Global Distance (4/9)

Screenshot: http://imageshack.com/a/img908/8144/wNaCxH.jpg

What I've tried so far:
  • Force update the pack - failed
  • Remove the .jar and .json files in <\Feed the Beast\versions\1.7.10>
  • Remove the "assets" and "libraries" folders in <:\Feed the Beast\>
  • Remove the entire <:\Feed the Beast\direwolf20_17> folder
Only when I remove the entire direwolf20_17 folder and then restart my game will it proceed to go past the bit posted above. Unfortunately, when I then close the game (via Quit Game) to restart it, it will stall on exactly the same point again.

So far, I've only been able to recreate this for my DW20 pack install, mostly since I hardly play any other packs atm.

Software installed and tried:
  • Latest FTB Launcher
  • Curse Minecraft Launcher
  • Java 7 (currently installed)
  • Java 8 (currently removed)
Perhaps anyone else can shed some light as to why this is happening of late and, most importantly, what I could do to fix it.

Cheers,
Bel*.
Try to allocate 1 more gb?
 
Try to allocate 1 more gb?

I've always run FTB with 4Gbs of RAM allocated, reduced it to 2 and worked upwards to 5...none of it matters. In total I have 12Gs of RAM to work with but, as many others have said before, MC is written in Java and the unfortunate thing to that is that the more RAM you provide, the more it will hog up.
 
if you have the log open, what is the last message what you get?
 
Something about the sound system. As with all other users who've reported this issue, an actual crash log is problematic since (I think?) it doesn't actually crash but simply stalls/hangs...at least, that's what I believe yet I'm no coding expert by far so interpreting the logs is quite difficult lol.

Anyways, below is the last portion of text that I typically see as my client hangs, incl. a link to the full log as posted to the Tech support forums as well.

[15:15:36] [Thread-16/INFO] [Mantle-STDERR]: [paulscode.sound.SoundSystemLogger]: OpenAL initialized.
[15:15:37] [Sound Library Loader/INFO] [Mantle-STDERR]: [paulscode.sound.SoundSystemLogger]:
[15:15:37] [Sound Library Loader/INFO]: Sound engine started

http://paste.feed-the-beast.com/view/18734e9e

Cheers,
Bel*.
 
Something about the sound system. As with all other users who've reported this issue, an actual crash log is problematic since (I think?) it doesn't actually crash but simply stalls/hangs...at least, that's what I believe yet I'm no coding expert by far so interpreting the logs is quite difficult lol.

Anyways, below is the last portion of text that I typically see as my client hangs, incl. a link to the full log as posted to the Tech support forums as well.

[15:15:36] [Thread-16/INFO] [Mantle-STDERR]: [paulscode.sound.SoundSystemLogger]: OpenAL initialized.
[15:15:37] [Sound Library Loader/INFO] [Mantle-STDERR]: [paulscode.sound.SoundSystemLogger]:
[15:15:37] [Sound Library Loader/INFO]: Sound engine started

http://paste.feed-the-beast.com/view/18734e9e

Cheers,
Bel*.
Try increasing the permgen. I've had my game hang there before and when I gave the game 256 or even 512 permgen, it stopped hanging.
 
As mentioned by others on the Tech forums yesterday evening, I tried disabling the splash.properties file in my minecraft/config folder and changed the value from TRUE to FALSE.

For now, it seems to have solved the problem. Will post here if it returns.

Bel*.