Issue description

Mekanism: Mekanism-1.21.1-10.7.10.73
Neoforge: 21.1.127
I have set up a nuclear fission reactor to run continuously, producing spent nuclear waste. During the day, the waste is processed into polonium, and at night, it is processed into plutonium. With a large number of processing machines (e.g., 36 machines processing waste), the chunk crashes within 3-8 hours. With a smaller number of processing machines (e.g., 10 machines), the chunk crashes after 10+ hours.

Steps to reproduce

1. Set up a nuclear reactor using sodium as a coolant that continuously and stably produces nuclear waste, with a burn rate of 64 or higher. Also, set up machines to process the waste into polonium, plutonium, and antimatter.(Ensure this is running on a server, that the chunk is continuously loaded, and that the production line runs stably without any downtime or other issues.)
2. Allow the production line to run continuously for 8-12 hours; the chunk should crash by then.

Minecraft version

1.21.1 (Latest)

NeoForge version

21.1.127

Mekanism version

10.7.10 (Latest)

Other relevant versions

No response

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

No response

Please supply the debug log

Please supply the debug log

2025-03-02-3.log

any chance you can grab the region file from the server? and identify the chunk

it sounds like what happens when there are a bunch of item entities being dumped into the world, which is not something mekanism tends to do