I don't think that this is a bug, but it is really annoying.
I don't know how exactly Mojang do benchmarks, but 40% time of CPU is spent on a garbage collector.
For instance, version 1.12.2 spends only 1% for GC.
Minecraft's allocation rate is around 100 ⚠️ megabytes per second.
Most allocations are Vec3 objects for math, (why are they not mutable?).
[media]
UPD: Yes, 1.12.2 is kinda old,but it's the last version before render engine/codebase rewrite.
[media]
UPD2: Allocation rate above is actually not vanilla, it was OptiFine + tons of stuff removed from the client, math objects made mutable, axis boxes made mutable and so on.
Vanilla:
Attachments
Comments 4
I reported one leak with textures. (in another issue)
I would consider that as a bug actually, because of such a "hollow throwing of memory into the wind".
This is not normal at all.
It's like Spring framework is used, but in Minecraft.
We only accept bug reports about performance issues if they point out a specific cause for performance issues, otherwise they're not useful to the developers at all.
Please create separate issues for separate memory leaks / issues you find.
I've provided screenshots where developers can see what exactly eats up whole memory, and they can do that by themselves,.
The only problem is that they continue using not mutable objects, use more stream API. API is awesome by it's design, can't agrue with that, but it's NOT cheap.
It's a game, where every second frame is important, and Mojang just ruin it.
Are there any specific memory leaks you want to point out (in the latest version 1.15.2 or the latest development version 1.16-pre1, that is)? Otherwise this is not really a valid bug report.