Lag spike to 0fs [0.2.9 - 1.21.11]

Versions

Minecraft: 1.21.11
Fabric Loader: 0.18.4
Voxy: 0.2.9-alpha

OS: Linux (6.12.63)
CPU: 16x AMD Ryzen 7 7800X3D 8-Core Processor
GPU: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 (Supports OpenGL 3.3.0 NVIDIA 590.48.01)
Driver Version: 590.48.01

Description

The lag spikes from 0.2.8 when the world was loading, are gone. I believe these were an issue with the Nvidia driver.

However, now while moving through the world I'll get lag spikes that freeze the entire game

Logs

https://mclo.gs/7Er7w5X

For logs I opened my world, spun around to ensure no loading lag, then flew in a set direction until the a lag spike happened, then immediately paused during the lag spike and left the game when the game stopped lagging and the pause menu appeared.

Snippet from around the lag spike

[16:20:42] [Render thread/INFO]: Resizing Dynamic Transforms UBO, capacity limit of 2 reached during a single frame. New capacity will be 4.
[16:20:42] [Render thread/INFO]: Resizing Dynamic Transforms UBO, capacity limit of 4 reached during a single frame. New capacity will be 8.
[16:20:43] [Render thread/INFO]: Resizing Dynamic Transforms UBO, capacity limit of 8 reached during a single frame. New capacity will be 16.
[16:20:43] [Render thread/INFO]: Resizing Dynamic Transforms UBO, capacity limit of 16 reached during a single frame. New capacity will be 32.
[16:20:44] [Render thread/INFO]: Resizing Dynamic Transforms UBO, capacity limit of 32 reached during a single frame. New capacity will be 64.
[16:20:45] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 2097152
[16:20:45] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 4194304
[16:20:45] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$SyncResults]: Expanding scatter update buffer to 24800
[16:20:47] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 8388608
[16:20:47] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$SyncResults]: Expanding scatter update buffer to 37360
[16:20:47] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$SyncResults]: Expanding scatter update buffer to 56160
[16:20:47] [Render thread/WARN]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager]: Large amount of copies, lag will probably happen: 600
[16:20:47] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 2097152
[16:20:47] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 4194304
[16:20:48] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$ComputeMemoryCopy]: Resizing scratch data buffer to: 8388608
[16:20:48] [Async Node Manager/INFO]: [me.cx.vy.ct.ce.rg.hl.AsyncNodeManager$SyncResults]: Expanding scatter update buffer to 24720
[16:21:11] [Server thread/INFO]: Saving and pausing game...

Start by reproducing the reported flight-through-world scenario on the listed Minecraft, Fabric Loader, Voxy, Linux, and NVIDIA versions, then inspect the linked log around the AsyncNodeManager resizing and large-copy messages. Compare the Render thread and Async Node Manager activity during a freeze; done means the reproduction no longer produces the reported full-game lag spike.