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
Crash on server start - Still got a ConcurrentHashMap in WorldTick #1000
Comments
Is your server on J8? And what version of IE are you on? Edit: Wait a second, that's actually weird. Log says you're running 0.7.3. I can't identify your Java version, but theoretically it shouldn't matter. Dafuq? |
yeah i removed my comment too ... it's a compiled 1.7 java .. i presume it's based in the same basic source as this strange commercial "Xnig" version (+ it's extensions) and he compiled it on arch linux ohhh now i get it ... nice one, the linux java version is far further in patches as the windows version .. thx oracle for keeping your versioning scheme so (in)consistent |
Yeah but with IE 0.7.3 Java version shouldn't make a difference. I make the cast to Map, which should disregard that keyset bogus. |
Um, this is probably my fault... I just checked the line the crash happens on and it is from my new drill animation code. I call |
WELP. Also, this is issue #1000, so be proud of yourselves people, you break this mod waaaay too much. |
IE seems to be getting all the powers of 10 this week... My last PR contained 2 commits, one of them was the 1000th commit on master, the other one was my 100th commit to IE, and now we got issue/PR 1000 as well! |
And you are also to blame for the 1000th issue xD |
Thanks guys, That's basically what I thought would be happening. Time for a bottle of apple juice (fermented or otherwise) it is then. |
As seen in our crashed attempt to start up a server:
http://pastebin.com/kpBJpGmf
The ConcurrentHashMap.KeySet() thing (issue #983) is happening somewhere else.
What surprises me greatly is that my personal client system for composing the modpack has no such error nor issue running java v 8u60. It only occurs when trying to start our dedicated server machine.
The text was updated successfully, but these errors were encountered: