You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
It doesn't generate a particularly specific detail in the log as to what causes it, however I can confirm having tested with and without TiCompend in the pack, that version 1.4.2.38 has a critical memory leak problem. It will cause the jre to request HUNDREDS of gb in ram, immediately crashing the instance and various other ongoing programs. My last dump shows the environment requested 1530416 megabytes for a new::chunk, which clearly not even a home server could provide, as that is literally over a terabyte in ram!
Without TiCompend in the pack, everything runs just fine, and not even once does it attempt to pull something so drastic.
The text was updated successfully, but these errors were encountered:
It doesn't generate a particularly specific detail in the log as to what causes it, however I can confirm having tested with and without TiCompend in the pack, that version 1.4.2.38 has a critical memory leak problem. It will cause the jre to request HUNDREDS of gb in ram, immediately crashing the instance and various other ongoing programs. My last dump shows the environment requested 1530416 megabytes for a new::chunk, which clearly not even a home server could provide, as that is literally over a terabyte in ram!
Without TiCompend in the pack, everything runs just fine, and not even once does it attempt to pull something so drastic.
The text was updated successfully, but these errors were encountered: