-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
[1.9.4] java.util.ConcurrentModificationException #3361
Comments
Believe it or not, not one of those crashes mentions Mekanism at all. Likely why minimalistic modpacks did not experiencing crashes as often. I'd suggest opening issue reports to the developers of the mods mentioned in the stack traces. |
Interesting, because all of it is fixed by removing Mekanism, but okay I will. |
Mekanism is handling network packets on the wrong thread which is likely causing the issue with all these mods. Ever since 1.8.9 IMessageHandler is no longer called from the main thread, so if you want to interact with pretty much anything from Minecraft you need to wrap that code in a Runnable and pass it to Minecraft.getMinecraft().addScheduledTask() / the equivalent method for servers which I believe is in WorldServer. See the warning in the Forge ReadTheDocs for info on this. |
Thanks for the heads up. Should be fixed in this commit: e4aed3f |
I have been getting a few of these as I'm testing Mekanism in my modpack:
When I first loaded the world: http://pastebin.com/JvpH45uh
When I placed a pipe: http://pastebin.com/2K2nHHCT
When I took Planks out of the Precision Sawmill: http://pastebin.com/7yKQ9EbK
Doesn't seem to be happening in a minimalistic modpack (JEI, Journeymap, Inventory Tweaks and Mekanism)
Edit: got one with minimalistic modpack when trying the oredictionaryficator:
Crash Report: http://pastebin.com/yYMsSmrr
Log: http://pastebin.com/3xkazrpm
and more:
Log: http://pastebin.com/u2VPzQnj
The text was updated successfully, but these errors were encountered: