Game crashes randomly when Entity Culling and Mekanism are installed
pietro-lopes opened this issue · 5 comments
Bug Description
Players are reporting this massively when using Mekanism pipes/blocks
For this instance player said the following:
Trying to place ultimate item pipe from mekanism on the reprocessor from extreme reactors this time
Reproduction Steps
Trying to place ultimate item pipe from mekanism on the reprocessor from extreme reactors this time
Log File
Crash Report
This is not a bug with Sodium. Your other mods are corrupting the game's memory and Sodium is crashing when interacting with those corrupted data structures.
You need to do a binary search on your list of installed mods until you find the one causing memory corruption, and report it to their authors.
I debugged this issue myself in the ATM server; it seems like Entity Culling (the async mod) allows Mekanism's culling code to run on a different thread, and that culling code has a rare case that can cause a new block entity to be added.
Going to re-open this since what information we have strongly points to an issue between Entity Culling and Mekanism.
We may consider adding Entity Culling to the list of incompatible mods, since these kinds of memory corruption bugs are frequent and very difficult to debug.
I've merged a patch which tries to handle the crash so that a more helpful error message is shown:
2d63bec
This does not fix the crash -- it is only diagnostics.
Nothing we can do about this. I don't want to add Entity Culling to the list of incompatible mods, even though I'm of the opinion that it is impossible for it to work properly when other mods are installed.
My recommendation is that users do not use Entity Culling, else they risk world corruption and random crashes like this. For people who insist on using it, they will just have to pay attention to crashes and deal with them appropriately.