This issue does not just occur when blocking Minecraft.exe on the Firewall.
It also occurs when you are in Offline mode or can not establish a connection for other reasons.
Therefore it needs to be fixed either way. Dealing with 150 MB log files filled with the same 7 lines of information does not benefit Mojang either.
The fix for this is for the logger to check if a connection could be established once.
If the connection was unsuccessful it could:
A) trigger a log every 2^n seconds to try for reconnection.
B) log once and ignore the failed connection afterwards
c) log to switch to offline mode so logging excludes network related logging.
This might be even easier if you filter logging messages in the first place to avoid reoccurring messages.
Maybe through a queue that checks the occurrences of a given message and only returning the counter + Message + TimeSpan or smh.
Just a thought though.
This still occurs.
I have some screenshots to confirm this and will share them later today.
I also checked if this occurs in 1.19 but F3 View GPU usage there seems to match what the task manager reports.
I'll test some more today and share my findings.
If you have any suggestions what to test feel free to share them
Fixed for Offline mode. Thank you
Sadly not fixed when blocking MC Launcher on Firewall.
Unfortunately not blocking this is not an option for me.
Also I am not an expert when it comes to logging data but this can't be good in the long run if this does not get fixed at some point... If the app gets unblocked at some point it would upload like 5gb of useless data to the server...
(Useless in the sense that it will repeatedly log the same 5 lines)
MC-260205
MCL-23077
This issue does not just occur when blocking Minecraft.exe on the Firewall.
It also occurs when you are in Offline mode or can not establish a connection for other reasons.
Therefore it needs to be fixed either way. Dealing with 150 MB log files filled with the same 7 lines of information does not benefit Mojang either.
The fix for this is for the logger to check if a connection could be established once.
If the connection was unsuccessful it could:
A) trigger a log every 2^n seconds to try for reconnection.
B) log once and ignore the failed connection afterwards
c) log to switch to offline mode so logging excludes network related logging.
This might be even easier if you filter logging messages in the first place to avoid reoccurring messages.
Maybe through a queue that checks the occurrences of a given message and only returning the counter + Message + TimeSpan or smh.
Just a thought though.
This still occurs.
I have some screenshots to confirm this and will share them later today.
I also checked if this occurs in 1.19 but F3 View GPU usage there seems to match what the task manager reports.
I'll test some more today and share my findings.
If you have any suggestions what to test feel free to share them
Fixed for Offline mode. Thank you
Sadly not fixed when blocking MC Launcher on Firewall.
Unfortunately not blocking this is not an option for me.
Also I am not an expert when it comes to logging data but this can't be good in the long run if this does not get fixed at some point... If the app gets unblocked at some point it would upload like 5gb of useless data to the server...
(Useless in the sense that it will repeatedly log the same 5 lines)