Problem with latest.log generating multiple GBs of data per play session as of recent

@FwgKing

I no longer get massive files. On average mine are about 25 MB and I am guessing from mob farming with command macros. Here are the answers.

1) fabric
2) 1.16.5
3) command macros, fabric api, optifabric, mod menu
4) not sure but assuming mod farming.

 

So there have actually been a few issues I've discovered that result in stupidly large log files. Still waiting on a few more inputs to investigate further into, but as for now, here's the simplest one to fix and it's with CommandMacros.

DO NOT make a macro and not implement a macro button with it/to toggle it, or you will be spammed 60 times a second like --->

Spoiler: 1 sec of errors

[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1
[16:50:11] [main/ERROR]: ########## GL ERROR ##########
[16:50:11] [main/ERROR]: @ Pre render
[16:50:11] [main/ERROR]: 65539: Invalid key -1

Still waiting on more replies to make sure I've zoned on the other issues, but definitely working on it.

 

Update on the latest findings.

Still could be many things that create large files, but here's one of them that does a few k mb a minute.

So to start things off, when switching servers using a completely vanilla client on 1.16.5, I get this message -->

Spoiler: Error Message

[17:36:10] [Render thread/FATAL]: Error executing task on Client
java.lang.NullPointerException: null
at ddn.d(SourceFile:199) ~[1.16.5.jar:?]
at dwu.a(SourceFile:2156) ~[1.16.5.jar:?]
at ri.a(SourceFile:122) ~[1.16.5.jar:?]
at ri.a(SourceFile:16) ~[1.16.5.jar:?]
at ol.a(SourceFile:21) ~[1.16.5.jar:?]
at ol$$Lambda$3400/1697815840.run(Unknown Source) ~[?:?]
at aob.c(SourceFile:144) [1.16.5.jar:?]
at aof.c(SourceFile:23) [1.16.5.jar:?]
at aob.y(SourceFile:118) [1.16.5.jar:?]
at aob.bl(SourceFile:103) [1.16.5.jar:?]
at djz.e(SourceFile:1015) [1.16.5.jar:?]
at djz.e(SourceFile:681) [1.16.5.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:215) [1.16.5.jar:?]

As it is just one message, it's not too alarming in itself. But, when connected to SkyBlock for any amount of time, You get this message, spammed almost 1k times a second in logs -->

Spoiler: Error Message

[17:48:02] [Render thread/INFO]: [STDOUT]: Negative index in crash report handler (0/21)
[17:48:02] [Render thread/WARN]: Exception loading entity:
u: Loading entity NBT
at aqa.f(SourceFile:1663) ~[1.16.5.jar:?]
at aqe.a(SourceFile:473) ~[1.16.5.jar:?]
at aqe$$Lambda$3672/638223261.accept(Unknown Source) ~[?:?]
at x.a(SourceFile:402) ~[1.16.5.jar:?]
at aqe.a(SourceFile:472) ~[1.16.5.jar:?]
at aqe.b(SourceFile:535) [1.16.5.jar:?]
at aqe.a(SourceFile:516) [1.16.5.jar:?]
at bqz.d(SourceFile:254) [1.16.5.jar:?]
at ecp.a(SourceFile:22) [1.16.5.jar:?]
at ecp.a(SourceFile:12) [1.16.5.jar:?]
at ecd.a(SourceFile:107) [1.16.5.jar:?]
at ecd.b(SourceFile:96) [1.16.5.jar:?]
at ecd$$Lambda$3668/1920137262.run(Unknown Source) [1.16.5.jar:?]
at ecd.a(SourceFile:128) [1.16.5.jar:?]
at ecd.a(SourceFile:96) [1.16.5.jar:?]
at eae.a(SourceFile:1260) [1.16.5.jar:?]
at dzz.a(SourceFile:727) [1.16.5.jar:?]
at dzz.a(SourceFile:546) [1.16.5.jar:?]
at djz.e(SourceFile:1048) [1.16.5.jar:?]
at djz.e(SourceFile:681) [1.16.5.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:215) [1.16.5.jar:?]
Caused by: java.lang.ClassCastException

After extensive testing through every available version, and with various client loaders, the problem seems to arise from 1.16 and up. This is the only group of versions that receive any error message currently for myself.

Weird problem arises when I have someone else test the problem being "Users Connecting to SkyBlock on 1.16 and up get error spammed", with the exact same replication steps on a completely vanilla client, and their set of errors is nothing like mine being -->

Spoiler: Test Person #1's Error

[02:59:29] [Render thread/FATAL]: Preparing crash report with UUID (REMOVED)
[02:59:29] [Render thread/INFO]: [net.minecraft.crash.CrashReport:func_85057_a:340]: Negative index in crash report handler (0/32)
[02:59:29] [Render thread/WARN]: Exception loading entity:
net.minecraft.crash.ReportedException: Loading entity NBT
at net.minecraft.entity.Entity.func_70020_e(Entity.java:1510) ~[?:?]
at net.minecraft.entity.EntityType.lambda$loadEntityUnchecked$2(EntityType.java:458) ~[?:?]
at net.minecraft.entity.EntityType$$Lambda$4930/231154485.accept(Unknown Source) ~[?:?]
at net.minecraft.util.Util.func_215077_a(Util.java:414) ~[?:?]
at net.minecraft.entity.EntityType.func_220330_a(EntityType.java:455) ~[?:?]
at net.minecraft.entity.EntityType.func_220343_b(EntityType.java:513) [?:?]
at net.minecraft.entity.EntityType.func_220335_a(EntityType.java:495) [?:?]
at net.minecraft.world.spawner.AbstractSpawner.func_184994_d(AbstractSpawner.java:251) [?:?]
at net.minecraft.client.renderer.tileentity.MobSpawnerTileEntityRenderer.func_225616_a_(SourceFile:22) [?:?]
at net.minecraft.client.renderer.tileentity.MobSpawnerTileEntityRenderer.func_225616_a_(SourceFile:12) [?:?]
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_228855_a_(TileEntityRendererDispatcher.java:126) [?:?]
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.lambda$renderTileEntity$0(TileEntityRendererDispatcher.java:101) [?:?]
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher$$Lambda$4764/1923298070.run(Unknown Source) [?:?]
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_228853_a_(TileEntityRendererDispatcher.java:185) [?:?]
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_228850_a_(TileEntityRendererDispatcher.java:99) [?:?]
at net.minecraft.client.renderer.WorldRenderer.func_228426_a_(WorldRenderer.java:1798) [?:?]
at net.minecraft.client.renderer.GameRenderer.func_228378_a_(GameRenderer.java:1022) [?:?]
at net.minecraft.client.renderer.GameRenderer.func_195458_a(GameRenderer.java:693) [?:?]
at net.minecraft.client.Minecraft.func_195542_b(Minecraft.java:976) [?:?]
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:607) [?:?]
at net.minecraft.client.main.Main.main(Main.java:184) [?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51]
at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:51) [forge-1.16.4-35.1.4.jar:35.1]
at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$424/143295000.call(Unknown Source) [forge-1.16.4-35.1.4.jar:35.1]
at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-8.0.6.jar:?]
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-8.0.6.jar:?]
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-8.0.6.jar:?]
at cpw.mods.modlauncher.Launcher.run(Launcher.java:82) [modlauncher-8.0.6.jar:?]
at cpw.mods.modlauncher.Launcher.main(Launcher.java:66) [modlauncher-8.0.6.jar:?]
Caused by: java.lang.ClassCastException

At the very least through my few days of testing and log-diving, there is an issue with errors being spammed in logs while on SB using a version of 1.16 and up.

 

@FwgKing Awesome job looking into this and reproducing it. Based on the stacktrace:

You said this is being logged hundreds of times per second - that would definitely be the reason behind the massive logs.

I was able to track down some bug tickets open about this on Mojang's Jira board:
https://bugs.mojang.com/browse/MC-198460
https://bugs.mojang.com/browse/MC-189565

The gist of this is:

• Mob spawner rendering is buggy for: bees, enderman, polar bears, wolves, piglins, evoker fangs.
  • The image rendering fails, and logs a message each and every time. This rendering happens at the rate of your framerate. Hence, many logs per second.
• This will be supposedly fixed in the 1.17 release.
• We are SOL until 1.17.

This does not appear to be ECC specific, and appears to be a bug with 1.16 Minecraft versions in general.