mojira.dev
MC-152587

Highish tick speed causes a memory leak and frame drops.

Set your tick speed to something like 30, and plant a bunch of trees. Memory usage (normally at ~30%) quickly grows from 30% to 75% (max 75%) and drops back to 30%, causing frame drops when it releases the memory.

I could attach the actual world to test, with the tick speed already set, but it's too large (25MB)

Linked issues

Comments 3

Duplicate of MC-76117.

Don't change tick speed if your computer can't handle it.

@violine1101 I can reproduce this with a tick speed of 3, it's just not as fast (to clarify by not as fast I mean the memory usage cycle described below doesn't happen as fast).

In any case, it should not be following this pattern of holding memory until a certain point, and releasing it, no matter how much memory I am running it with.

In any case, it should not be following this pattern of holding memory until a certain point, and releasing it, no matter how much memory I am running it with.

That's how Java garbage collection works, Minecraft can't change that.

user-cd26d

(Unassigned)

Unconfirmed

Performance

Minecraft 1.14.2 Pre-Release 2

Retrieved