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

1.16.5 Dedicated server crash on autocrafting - Exception in server tick loop java.util.ConcurrentModificationException: null at appeng.util.item.ItemList$ChainedIterator.next #5158

Closed
ProsperCraft opened this issue Apr 16, 2021 · 7 comments · Fixed by #5160
Assignees
Labels
bug Self explanatory?

Comments

@ProsperCraft
Copy link

Describe the bug
A player on our server says he was autocrafting Mekanim things, and the server went down, he was the only player on at the time.

To Reproduce
Asking him for steps to reproduce.

Additional context
Crashlog-
https://gist.github.com/ProsperCraft/82ef431b0d11ec862898bf98e0bbaeea

Environment
appliedenergistics2-8.3.0-alpha.3
forge-1.16.5-36.1.2
Dedicated server.
TownCraft TWO for 1.16.5 modpack

@shartte
Copy link
Member

shartte commented Apr 16, 2021

Do you know what the player was crafting?

@ProsperCraft
Copy link
Author

Mekanism power cables, but when they did it again, it did not crash.

shartte added a commit that referenced this issue Apr 17, 2021
… crafting CPU when dumping items into the network after a job was completed.
@yueh
Copy link
Member

yueh commented Apr 17, 2021

performant might also be a cause here.

@ProsperCraft
Copy link
Author

@shartte
Copy link
Member

shartte commented Apr 17, 2021

@ProsperCraft We've just pushed alpha.4 that includes more debugging code to hopefully track the root cause of this down.
In the meantime, I presume the craft that caused this was the same again? Can you describe the pattern that the player is using to craft?

@zpprsprk
Copy link

zpprsprk commented Apr 18, 2021

I just experienced a similar issue. I was running version alpha.4 and this is the part of the server log file when the crash happened.
https://gist.github.com/zpprsprk/57247faf16fe6affb473826e5d9f4fa3
Crash report: https://gist.github.com/zpprsprk/555b018f2e9d62dae3480e52d18a93d9
I was auto crafting with a mekanism ultimate smelting factory. The pattern was a processing pattern for 64 exnihilo nickel ore chunks to 64 nickel ingots. It first happened when I requested 1001 ingots (it said it would do 1024). After restarting the server, I asked for 128 with no issues, then 1024 (exactly) with no issues, then again 1001 (that it said it would do 1024 again) and triggered the crash again.

@yueh yueh self-assigned this Apr 18, 2021
@yueh yueh added the bug Self explanatory? label Apr 18, 2021
@yueh
Copy link
Member

yueh commented Apr 18, 2021

@zpprsprk Thanks, could reproduce it thanks to the description

shartte added a commit that referenced this issue Apr 18, 2021
…ssing recipe, the CPU may still be waiting for items when it completes the job. Do not wait for these items and instead just finish the job cleanly.
yueh pushed a commit that referenced this issue Apr 18, 2021
…ssing recipe, the CPU may still be waiting for items when it completes the job. Do not wait for these items and instead just finish the job cleanly. (#5160)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Self explanatory?
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants