Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mekanism Reactor Output Causes Chunk Crash (MC 1.21.1) #8343

Open
leonary opened this issue Mar 2, 2025 · 3 comments
Open

Mekanism Reactor Output Causes Chunk Crash (MC 1.21.1) #8343

leonary opened this issue Mar 2, 2025 · 3 comments

Comments

@leonary
Copy link

leonary commented Mar 2, 2025

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.

Image

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

@thiakil
Copy link
Member

thiakil commented Mar 2, 2025

Please supply the debug log

@leonary
Copy link
Author

leonary commented Mar 2, 2025

Please supply the debug log

2025-03-02-3.log

@thiakil
Copy link
Member

thiakil commented Mar 12, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants