Closed SvEgiiVEteR closed 7 years ago
Those are TRACE-level logs which are normally only used for debugging; you shouldn't need anything more than the default INFO-level for normal play. Any particular reason why you'd need TRACE-level enabled?
@delvr I don't know..didn't include any
java.exe" -Xms3000m -Xmx3500m -XX:MaxPermSize=480m -XX:PermSize=480m -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump "-Dos.name=Windows 10" -Dos.version=10.0 -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn512m -Djline.terminal=jline.UnsupportedTerminal
but when i put mod:
was fml-client-1.log - 12MB
with mod fml-client-latest.log - 480MB
and a lot of a lot of log spam.
https://gist.github.com/b674f63a5b887e0eac2eb90316110a44
or
https://gist.github.com/19c5b299f2eb6db73a00738aeeb36d11
Checking on the server Left the current mode farseek and the same spam in the log https://gist.github.com/SvEgiiVEteR/7e6dff51526d4366e0851926b30e3333#file-2017-06-22_19-43-58-txt-L5345 In a full file of 500,000 lines. There is even more
OK I'm not seeing the Trace statements on my client but I do see it on the server. I'm uploading a patch today to remove it.
Sorry for the delay - fixed in Farseek 1.7.10-2.0.1.
Farseek-1.7.10-2.0.jar Streams-1.7.10-0.3.jar https://gist.github.com/597c09e4b3d9078fe12673bfdb25e846 fml-client-latest 186 MB