Memory leak for VolatileField Class, method finalize()
tauchet opened this issue ยท 1 comments
Describe the bug
One way to explain the bug is that after some time, thanks to one of its used classes, the memory is left with residues of worlds that want to download, therefore in games that are widely downloading and loading preloaded worlds, it stays in memory and therefore over time, this leads to a bottleneck that could cause the server to crack or just shut down.
To Reproduce
Basically it occurs when worlds are unloaded in on-time, it causes the worlds to be trapped in containers of the VolatileField class for some reason and since the class is modified it is not finalized and therefore a reference remains in memory.
Basically researching a little about the code and seeing, that they make use of the finalize method, is there some way that the real method is executed, because without this worlds or any reference, they get trapped by that class, then it is a danger for the ram memory .
4.5.1