-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Frequent ConcurrentModificationException potentially breaks capabilities of other mods #177
Comments
Thanks for reporting! |
Hmm, something is definitely going wrong there indeed. Note to self: |
@andriihorpenko The issue should be fixed in the last commit. Before I publish this release, could you try out the latest dev build to confirm that it fixes the problem on your end? |
Sure, I will install it on all servers and let you know how it goes. It may take some time to test it out, hopefully not more than a day. |
@rubensworks you can safely publish this build. There is no |
Excellent, thanks for checking! |
Issue type:
Short description:
There is an ongoing issue with Mekanism (mekanism/Mekanism#7831) and after some investigation we located an exception thrown to the log on server boot. More specifically, a
ConcurrentModificationException
exception with stacktrace pointing to CyclopsCore.Little background: I run 5 servers and sometimes after a server reboot some Mekanism structure stop accepting liquid. I checked out logs of 5 servers and 3 out of 5 had a
ConcurrentModificationException
thrown. Interestingly, servers with that exception had problems with Mekanism, while the rest of them had no issues. This suggests that that might be the actual root cause.Steps to reproduce the problem:
Unfortunately, there are no specific reproduction steps and this happens inconsistently. This happens 1 out of 3 server boots.
Expected behaviour:
Not potentially breaking capabilities of other mods on server load.
Versions:
Log file:
Exceptions thrown on lines: 308, 400, 492
https://bytebin.lucko.me/zuCWjPaT0I
The text was updated successfully, but these errors were encountered: