Minecraft crashed with a stack trace

Describe the bug
Crash

To Reproduce
No idea how to reproduce. I was moving away from the area so the chunk may have been unloading.
I had played many hours with a sizeable ae2 network, the same mods, and left the area many times without a crash however. Judging by the stack trace it shouldn't be that hard to add a safety check though even if postChange shouldn't be in a situation where it's popping from an empty ArrayDeque

Additional context
stack trace

Environment
Windows 10
Single player.
I added Optifine and TickDynamic to the mod pack to attempt to improve lag.

• Minecraft Version: 1.12.2
• AE2 Version: rv6-stable-2
• Forge Version: 14.23.5.2769

I just looked at the code myself, and I have no idea how this crash was even possible. I know ArrayDeque is not thread-safe, but it does not seem possible to fail the way it did, even with multiple threads calling into this class. Close this if you like. If I discover my RAM is going bad or something, I'll come back and update.

Most likely a duplicate of #3777.