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.

Sign up for GitHub

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

Jump to bottom

Memory leak from client renderer #561

Closed
CelestialAbyss opened this issue Oct 3, 2023 · 0 comments
Closed

Memory leak from client renderer #561

CelestialAbyss opened this issue Oct 3, 2023 · 0 comments
Labels
1.19 1.20 bug fixed in next release

Comments

@CelestialAbyss
Copy link

Expected Behavior

Even after a long testing session, this shouldn't happen.

Actual Behavior

Memory leak occurs instead, causing a crash after a certain amount of time.

Steps to Reproduce

  1. Play for a prolonged amount of time after picking up and placing down blocks with Carry On...
  2. Eventually the memory leak occurs (debug log has been attached below)

Version of Minecraft, Carry On, Forge/Fabric

MC version: 1.19.2
Carry On version: 2.1.1.21
Forge version: 43.2.21

Screenshots encouraged

No screenshots, but I do have a debug log: https://gist.github.com/CelestialAbyss/9e61697a48c4da2ec18e73814191914a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.19 1.20 bug fixed in next release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Tschipp @CelestialAbyss