Bulk compression potentially using too much memory

[zer0cares]

crash-2024-01-22_08.05.24-server.txt

Worked fine before, then the only change was that the forge version on the server updated, and now the server doesn't start. Tried reverting to the older forge version and its still crashing, with the crashlogs pointing to MEGACells.

Any help would be appreciated, thanks!

[xSamTheKingx]

Same issue here please help anyone?

[62832]

Are we talking Forge or NeoForge?

[zer0cares]

Forge

…

On Mon, Jan 22, 2024, 9:23 AM 90 ***@***.***> wrote: Are we talking Forge or NeoForge? — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMGACAG4ZCP2AUGKAM52DG3YP24EHAVCNFSM6AAAAABCE5ZL2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGY2TOMJWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xSamTheKingx]

Forge_1.20.1_47.2.19

[62832]

Then I would suggest using NeoForge instead since I'm not really providing support for Forge versions beyond 47.1.3.

EDIT: Having just tried out a Forge 47.2.19 installation, I'm unable to reproduce this.

[xSamTheKingx]

Its the server ram caused the issue. I upgraded ram to 16GB and now its good
Its strange how much ram atm9 needs as i only have 3 players on the server.

[62832]

Yes, I suppose the initial caching process for the bulk compression service would be quite memory-intensive, though this certainly isn't ideal.