Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game consistently runs out of memory since updating #18768

Open
3 tasks done
truepurpledino opened this issue Jan 14, 2025 · 1 comment
Open
3 tasks done

Game consistently runs out of memory since updating #18768

truepurpledino opened this issue Jan 14, 2025 · 1 comment
Labels
Crash Status: Triage Issue awaiting triage. Remove once this issue is processed

Comments

@truepurpledino
Copy link

Your GTNH Discord Username

purpledino

Your Pack Version

2.7.2 nightly817

Your Server

Private server

Java Version

Java 21

Type of Server

Vanilla Forge

Your Actions

Seems to happen more often when searching in an ME system or in NEI.
I have reports that another player is having the same issue on the stable version of 2.7.1, whilst maybe not having the issue on 2.7.0 (words from stratoz7 on discord).
My teammate (pink_evil on discord) has also had this issue happen since updating.
I have tried playing on a fresh instance of 2.7.2 nightly817 on singleplayer and seemed to have no issue playing there (in a new world), but on the same instance, when joining my own server, the issue occurred again.
Our world was updated from 2.6.1 to 2.7.2 nightly817 on a Debian machine, without issue, using the 2.7.2 nightly817 server pack.

This might be anecdotal, but memory usage in task manager is also always creeping up compared to 2.6.1 and seems to be higher after initially loading the pack than before.

If it matters: my specs are Ryzen 3600, Nvidia 3060, 16gb of ram, 8gb allocated, launcher is prism (unchanged from 2.6.1). my teammate's specs are ryzen 5600G, AMD gpu, 32gb of ram, 8gb allocated, java 17 (unchanged from 2.6.1).

Crash Report

Full log from game start to crash: https://mclo.gs/jsSMPOc

Crash log: crash-2025-01-13_00.12.19-client.txt

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the crash still exists will prompt us to investigate and reopen it once we confirm your report.
  • I can reproduce this crash consistently by following the exact steps I described above.
  • I have asked other people and they confirm they also crash by following the exact steps I described above.
@truepurpledino truepurpledino added Crash Status: Triage Issue awaiting triage. Remove once this issue is processed labels Jan 14, 2025
@Lithorn
Copy link

Lithorn commented Jan 27, 2025

I have noticed my client starts to have issues the longer I play, and I give it 8g of ram out of the 32g I have. Seems like its not releasing the garbage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crash Status: Triage Issue awaiting triage. Remove once this issue is processed
Projects
None yet
Development

No branches or pull requests

2 participants