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

Excessive Memory Usage #66

Open
restonic4 opened this issue Dec 23, 2024 · 1 comment
Open

Excessive Memory Usage #66

restonic4 opened this issue Dec 23, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@restonic4
Copy link

The JVM constantly crashes because surveyor us using to much RAM, this happens to me on client side and on my dedicated server.

If I remove the surveyor folders on the server and client, it works again.

image

The exact same error everytime:

[14:03:44] [Render thread/INFO]: [Surveyor] Loading data for minecraft:overworld
[14:04:19] [Netty Client IO #3/ERROR]: Registry remapping failed!
java.util.concurrent.TimeoutException: null

....

[14:04:35] [Render thread/INFO]: [Surveyor] Loading data for minecraft:overworld
[14:04:36] [Netty Client IO #3/INFO]: Received common config 'fallingtrees:fallingtrees_common' from server
[14:05:08] [Render thread/INFO]: [FANCYMENU] ScreenCustomizationLayer registered: out_of_memory_screen
[14:05:09] [Render thread/ERROR]: Out of memory
java.lang.OutOfMemoryError: Java heap space

This happens frequently on really modded enviroments, but it also happens on vanilla clients (only the mod and antique atlas 4), its harder, but it happens.

If i create a new server with a void generator, just nothing, tick frozeen and nothing going on, if i explore the exact same amount of chunks with and without the mod those are the stats:

Without the mod: 3.6GB / 8GB
With the mod 7.8GB / 8GB

Client side log file while joining my dedicated server:
latest.log

@restonic4 restonic4 changed the title Sever and client constant crashed related to memory usage. Sever and client constant crashes related to memory usage. Dec 23, 2024
@sisby-folk sisby-folk changed the title Sever and client constant crashes related to memory usage. Excessive Memory Usage Dec 23, 2024
@sisby-folk sisby-folk added the bug Something isn't working label Dec 23, 2024
@sisby-folk
Copy link
Owner

sisby-folk commented Dec 23, 2024

Yep, this is #63 - without a proper streaming system, exploring chunks will linearly scale the amount of memory usage. You do have to try really hard to generate untenable amounts of data (it's usually only possible in multiplayer or with a lot of time on your hands).
The size of your world/data/surveyor folder should be indicative: 400mb of data here (as retrieved from a server admin with 100+ players - I think it's about 8 million chunks? less if you have really big block palettes) equals roughly 24GB of memory usage in-game.
Because this is usually only possible on the server end or via sharing, you can set terrain = DISABLED in surveyor.toml ON THE SERVER ONLY as a workaround. Clients that already have too much save data will need to clear theirs from the data/surveyor folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants