Neal Savage

> In that case, here is some additional information: The issue only exists in Fabric Loader 0.14.x. Here is a crash report: > > ``` > [17:57:38] [main/ERROR]: A mod...

> Unfortunately, that's a different issue (see #74), which was indeed 100% caused by Quilt-on-Fabric hacks and was solved by not doing those hacks in the first place; This issue...

> No, beta.6 was still a Fabric-only release, with beta.7 doing it (this issue is older than it, after all); Whatever the issue is, it'll probably either going to affect...

MultiMC Console Output: https://pastebin.com/ns10y1ht Logs, latest: https://pastebin.com/cJ1sRKN2

It's happening to me too, constant memory leak logs. It's because of sodium. It doesnt happen to me unless I have sodium installed.

Yeah, it's still happening for me. It's really really bad.

Why has this still not been fixed? The issue has been identified for like 20 days or something. It's a literal game breaking bug, it should have been fixed immediately.

I already gave logs and information on another reporting of this issue.... It's not like I complained and gave no information. But, I can check real quick if it happens...

That was with literally only Sodium installed as a mod, not even anything like Fabric API. Hope that helps you out.

> @NealSavage Enable the "Memory Tracing" option and post logs with warnings again. That option may lower performance, but it will indicate where the memory leaked from. Where's that at?...