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

Memory leak when using LevelDB #272

Open
BlusteryS opened this issue May 18, 2024 · 1 comment
Open

Memory leak when using LevelDB #272

BlusteryS opened this issue May 18, 2024 · 1 comment

Comments

@BlusteryS
Copy link
Contributor

BlusteryS commented May 18, 2024

🐞 Bug Feedback

📝 Bug Description

When using LevelDB (no matter native or default), a large memory leak occurs. Objects appear that java cannot remove. In 5 minutes of flying around the world, about 1200 MB accumulated (not counting the 800 MB that is required for the start and login of the player).

When using anvil, even when loading chunks for 10-15 minutes, memory usage remains at ~ 800 MB (sometimes even less, it does not increase).

When using custom generators, values ​​can exceed 3 GB in a few minutes

I profiled the process through YourKit, but didn't find anything. 800 MB - not reachable to GC.

📸 Screenshots / Video

image
image

💻 OS and versions

image

  • Version: 1.20.80
  • Java: OracleJDK, GraalVM
  • Java version: 22
@BlusteryS
Copy link
Contributor Author

BlusteryS commented Jun 2, 2024

When using Parallel GC, OOM is not caught, but memory still grows to the maximum.

I think the problem is in the library providing the leveldb implementation, but Java profilers can't find the reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant