FTB Beyond Memory Leak

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • 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
G

Ghost942

Guest
Title FTB Beyond Memory Leak

Launcher Type Twitch Desktop App

Modpack FTB Beyond

Modpack version 1.5.3

Have you modified the pack? Yes

Link to log file N/A

Details of the issue I've been having this issue ever since I downloaded FTB Beyond through the Twitch Desktop App. Whenever I run Beyond, memory allocation will start around 1GB, then gradually make its way up to 4GB and peaking.

What's interesting about this is that as I am playing on my localhost server, memory allocation will continue to climb, even reaching 26GB of my max 32GB RAM (and at one point, 36GB/32GB). This then causes others on my server to have frame issues/stuttering/freezing/major lag.

The only solution I have found so far is to shut down my client (by this time slow to do anything (~30secs for a command)) and restart the client to free up my RAM.

Is there a fix for this? Is this a garbage collection that isn't getting purged correctly?

Also to note, this is 1.10.2 build, so anything related to 1.7.10 does not work, as I have browsed through many pages of that to no avail.

No log file to link to, as nothing in the log file gives any indication of why my memory climbs.

Upon request, I can provide images of when the client first started vs ten minutes in-game vs twenty minutes in-game. Image links will be through imgur.com

Additional Mods: FastLeaveDecay-MC1.10.2-1.2.3, MorePlayerModels_1.10.211nov16, VeinMiner-1.9-0.35.3.595a46c1b0
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
It sounds like you've allocated way too much ram to your client.

If you allocate too much it's going to cause issues like this when java garbage collection hits.

Rule of thumb: 1.7.10 - keep it 2,5 - 4GB
1.10.2 - 4-6GB
(this is ofc give or take a few up or down depending on other hardware, number of mods in pack etc.)

Try to reduce allocated ram and see if that helps, if not - post logs.

Instructions for getting the log can be found here:
http://support.feed-the-beast.com/faq/
 
G

Ghost942

Guest
http://paste.feed-the-beast.com/view/5ab0e161

Latest log file

I've reset memory allocation to "-Xms4G -Xmx6G" in the JVM arguments. Next question: how do I make the client stay with those arguments, as it will default back to "-Xms 1024M -Xmx4096M"?

EDIT: Can't start my client with a minimum of 4GB. "Failed to create the JVM" "Fatal Exception, Program will now close"
 
Last edited:

KingTriaxx

Forum Addict
Jul 27, 2013
4,266
1,333
184
Michigan
I've got the same problem, same version, without any tweaks to the pack. Starts on launch a 2.5GB of RAM and in half an hour climbs to 6GB of usage, with allocation at 4.
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
I've got the same problem, same version, without any tweaks to the pack. Starts on launch a 2.5GB of RAM and in half an hour climbs to 6GB of usage, with allocation at 4.

That's normal behavior of the jvm (you've allocated 4gb to minecraft, then other things in jvm needs some space as well to do stuff) - I don't see how this is the exact same problem as OP, he/she probably allocated all available ram on the machine - and that's causing OPs issues.
 
  • Like
Reactions: jikuja

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
I'd say that's perfectly fine, except I spend half of half-hour gaming session 'waiting for server...'

By the sound of this your problem is a different one, perhaps best addressed in a new thread where you give as much information as possible about your setup, the pack your using and most important - full log from when the error occurs.

Instructions for log can be found here:
http://support.feed-the-beast.com/faq/
 
M

Mr.Meeseeks

Guest
I have I think a nearly identical issue here. I'm using the recommended amount of client RAM allocation from the Twitch/Curse launcher ~6.4GB. I am also running the server on my W10 computer with 4GB allocated. The RAM will slowly climb until I run out and the only way to get it back is to reboot. This RAM seems to be used according to W10 but you can't see what is using it so I don't know if it's the client or server messing things up. I just upgraded to 1.6 FTB Beyond and the issue is still here.

In my case I have 32 GB ram minus 4-5 that Windows and other software takes up minus 6.4 for client minus 4 for server and that should leave me with 16 GB ram, but it uses all 32.
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
I have I think a nearly identical issue here. I'm using the recommended amount of client RAM allocation from the Twitch/Curse launcher ~6.4GB. I am also running the server on my W10 computer with 4GB allocated. The RAM will slowly climb until I run out and the only way to get it back is to reboot. This RAM seems to be used according to W10 but you can't see what is using it so I don't know if it's the client or server messing things up. I just upgraded to 1.6 FTB Beyond and the issue is still here.

In my case I have 32 GB ram minus 4-5 that Windows and other software takes up minus 6.4 for client minus 4 for server and that should leave me with 16 GB ram, but it uses all 32.

You should create your own topic.