#4964 opened by Unknown 2 years ago
https://git.lumine.io/mythiccraft/MythicMobs/-/issues/1583
its pretty related to this. I cant find the screenshot where i have the heapdump shown for modelengine but there was a ConcurrentHashMap holding references to world. Might be worth changing that to referencing the world UUID instead of the world object and the entity id instead of the entity object
Hey there! Just chiming in to confirm I'm also encountering this with Mythic Dungeons severely amplifying the problem due to its dynamic worlds. It's only been occurring as of the latest version of Model Engine. (4.0.6.1)
OP's suggestion to track world/entity ID is feasible, but another option would be to instead make use of WeakReference<ObjectType>, which would allow the object to still be referenced while opening it up to being GC'd.
Getting this as well, also multiple worlds, it's really bad, can't even get to a full day uptime without garbage collection shitting itself