So while there is memory available to be released, and potentially even free memory available, the process of releasing it is slow enough that it causes pauses whenever the GC is run.Īfter identifying the GC pressure issues fairly early on after the update, we began recommending users update their launcher if they are on one of the old pre-2.0 launchers (1.6, 1.5, and older). The garbage collector must keep track of these many different small allocations and handle releasing all of them, which is computationally expensive. The second is caused by many small allocations. Since most of the memory is in use, it is a difficult and slow process, leading to long pauses and lag. The garbage collector will pause the client until it is able to find enough memory to release to fulfil each allocation. It becomes difficult to allocate additional memory since it often first require the garbage collector to run.

The first is caused by there being very little free memory. There are two different types of pressure which we will cover: The cause of the lag issues have been due to Java garbage collection pressure. Note that this post is about client lag, which is the client dropping frames, and not network lag, which is the time between an action being done and the server receiving the action, nor server lag, which is when the server skips ticks, causing time to essentially stop. We now feel like we've identified and fixed the root cause, which this post is about. We did not have good answers for players at that time due to the confusion of receiving so many error reports, often conflicting, at the same time. This is a bit of a tech blog about the ToA release and the stability issues the client has been having, feel free to skip it if that isn't your thing.Īfter the release of ToA on Aug 24 we saw a large number of reports from users about the client destabilizing in ToA, either crashing, or running with low FPS.

Arch linux macbook pro right click