Memory usage increases continuously during gameplay #24

New Issue

2024-11-04T05:29:54Z

icarus7074 commented

2024-11-04 05:29:54 +00:00

(Migrated from github.com)

While the program is running, the memory usage keeps rising until all memory is exhausted.

A few minutes after the program started:

Some time later:

I'd say this is a pretty significant issue.

While the program is running, the memory usage keeps rising until all memory is exhausted. A few minutes after the program started: ![first](https://github.com/user-attachments/assets/e66712b4-5f24-4162-b67f-7ca09fb171f4) Some time later: ![real](https://github.com/user-attachments/assets/d46e4b25-9aab-4cec-bc90-c203cfdd382e) I'd say this is a pretty significant issue.

GelbEinhalb commented

2024-11-11 11:49:10 +00:00

(Migrated from github.com)

Are you sure this is a general issue and not just happening when loading chunks until the render distance is being reached?

In my experience, memory usage does spike initially while chunks are loading but then stabilizes once the target render distance is reached.

My observation

At startup, memory usage is around 115M:
When the render distance is set to 10, memory usage stabilizes at around 497M after initial loading:
Increasing the render distance to 25 and render height to 10 results in a peak of around 2.6G, which then remains steady:

It took some time for all those chunks to render, but as soon as the chunks variable stopped rising, I checked btop and took the screenshots. It seems that memory usage scales predictably with render distance and height settings but doesn't continually increase once the chunks are fully loaded. The spike is probably more a function of the initial loading process rather than a persistent memory leak.

How can you check?

To verify if this behavior matches what you are seeing, you could monitor the number of chunks loaded. This should provide a better insight into whether memory usage is tied to chunk-loading or if it continues to increase abnormally over time.

Are you sure this is a general issue and not just happening when loading chunks until the render distance is being reached? In my experience, memory usage does spike initially while chunks are loading but then stabilizes once the target render distance is reached. ### My observation 1. At startup, memory usage is around `115M`: ![btop-screenshot-1](https://github.com/user-attachments/assets/a5d8f7b3-f622-4011-853a-57c274be7921) 2. When the render distance is set to 10, memory usage stabilizes at around `497M` after initial loading: ![btop-screenshot-2](https://github.com/user-attachments/assets/59a6f70f-5bad-45f9-850b-1faef783bd0a) 3. Increasing the render distance to 25 and render height to 10 results in a peak of around `2.6G`, which then remains steady: ![btop-screenshot-3](https://github.com/user-attachments/assets/fd34063e-9d2b-4fce-a554-ea62beac5360) It took some time for all those chunks to render, but as soon as the chunks variable stopped rising, I checked btop and took the screenshots. It seems that memory usage scales predictably with render distance and height settings but doesn't continually increase once the chunks are fully loaded. The spike is probably more a function of the initial loading process rather than a persistent memory leak. ### How can you check? To verify if this behavior matches what you are seeing, you could monitor the number of chunks loaded. This should provide a better insight into whether memory usage is tied to chunk-loading or if it continues to increase abnormally over time.

Sign in to join this conversation.