-
Notifications
You must be signed in to change notification settings - Fork 55
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: java.util.NoSuchElementException: key not found: codechicken.lib.vec.BlockCoord@46cf #139
Comments
|
Confirmed. This has been happening in karelmikie3's electronics server: Bottlenet |
|
|
|
Issue MinecraftPortCentral/Cauldron#484 must be reopen-ed. :( Bug is still active. I can fix it locally using a chunk loader. |
|
Due to the number of times this bug has been reported, I'm going to leave this open, and repoint all similar bug reports here. This is a craftbukkit issue please report it to them. |
|
For the record, changing that config didn't fix it. |
|
I am useing regular forge and when I place a multiblock the client crashes but the server doesn't even have an error . @Chicken-Bones |
|
I need someone to provide me with a setup that I can replicate the issue with (regular forge) |
|
Probably get tons of these but , have a ts or Skype ? It would make it a lot easier to show and tell you how to replicate this @Chicken-Bones |
|
@Chicken-Bones ^^^^^ sorry , I run a server and this is a major issue |
|
@Chicken-Bones fixed it , there was an error in my config files somehow reset them and generated new ones , it now works perfectly |
|
That's very strange. |
|
So far, I can't replicate it without mcpc+. Exact same map, crashed first try with mcpc+, switched jar's and it stopped. Has gotten so bad that half of the people can't even log in without getting warped away. |
|
This was my crash report: http://pastebin.com/iiFfSXLu Server running mcpc+ Luckily in the spot it was crashing, there was only one thing in the area, an Applied energistics quantum bridge. Hope this helps, perhaps the issues lies in something in that chunk needing to be loaded in order for you to log in. |
|
Although my steps for reproduction are not the same, the crash is the same. It's not an issue with MCPC, I copied my server world to local and still have it. I can reproduce it easily, but uploading my 500MB+ world with 400MB+ of mods is not realistic. I have many "Dynamic Tank" multi-blocks from Mekanism in a structure I built for pure aesthetics (i.e. the multipart machine is not functional/valid) and when trying to destroy them "too quickly" I get the same crash over and over. I was running optifine but removed it, since it can mes with chunks. There are no other chunk-related mods/hacks installed, apart from ChickenChunks. The area was under a chunk loader from said mod, but I removed it and it made no difference. My educated guess is that it's a race condition with server ticks or something, possibly a bug with Forge Multipart? I tried manually updating Multipart to latest, again no difference. For now I'll just be patient and slow destroy these blocks, maybe I won't use them again :) EDIT: I should note that this problem for me only just started occuring today, I had destroyed many of these "Dynamic Tank" blocks in the same structure at super speed (Tartarite Pick) and got about halfway through until these crashes started happening at random. Being cautious/patient indeed solves it for my case so it's not a big deal for me, just thought I'd add my finds. |
|
Short form Not able to reproduce {it reproduces its self how it wants when it wants) Issue is a continuous problem with interesting behavior that is affecting several patrons of the server I play on server is unaffected but clients crash straight to desktop on the following reasons and conditions When logging in Remedy's *eventually is used loosely here 1-3 attempts are usually enough with very few cases of upto 7 times Chunkloaders do not help with the issue as in prevention or remedy appears to be of no effect Microblocks have proven to increase the amount of occurrences but are not limited to we have tested heavily built areas with microblocks to cause reproduction more often it is absolutely strange behavior that might require some tricky hook or coding to fix |
|
EDIT: Nevermind razorbhunter, you're already on Forge .965 My issue I think was a problem with Forge. Since updating my server (and client) to .965 I've been unable to reproduce it (could be because I started a new world though). |
|
Happens on 965. I haven't had this issue much since doing the chunk loading suggestion. |
|
issue is still well a issue 70% of our servers player base has now been affected by it and most of our player base has left with no wish to return from this issue.. its a chronic issue with all players living in my residential area on our server. it used to just crash one or 2 times while trying to log-in but now it does not fail crash is guaranteed pretty confident it has something to do with initializing something in the affected area or loading up of multiple chunks at one time causing confliction. on a side note I have had multiple crashs with the same error message while breaking thermal pipes or even multipart panels and covers,posts and so on rapidly so may it be possible that it has to do with many tileentites loading or unloading at once that have to do with forge multipart ? because I will honestly say I have well over 300 redstone conduits in my place and just as equal fluiducts floating around with covers and so on for asthetics only remedy is to get warped out on log-in and crash relogin at new location then travel back on foot and be fine until log out which have found logging out away from the area affect = good logging out in affected area = bad I can talk to Owner about setting up a working and testing environment of the server if anyone is willing to debug and figure out the issue |
|
I really want to resolve this issue, but I need a map and MCPC instance that causes the issue. (preferrably < 100Mb) Someone who has this happening 100%, please make a copy of your map. Delete chunks and dimensions that aren't relevant to reduce the size. And send me that with the server, and coordinates to warp to and relog at. |
|
If you haven't had this provided yet, I can do it. Let me know where to send the files? (ETA- this has been happening for a while in different places to different players - just nobody has reported it and I only noticed when I went to update my pack that the automatic crash delivery was chock-full of reports) |
|
Any file host/webserver (dropbox, mediafire, direct download etc) |
|
This bug is still happening, using build 244: http://pastebin.com/M5mBmU08 |
|
be48cfe (1.0.0.249) Should hopefully help with this issue, especially on login in MCPC |
|
I also have been getting this error: https://dl.dropboxusercontent.com/u/126850755/crash-2014-02-24_21.48.55-client.txt. I host a custom modpack that I pieced together and I am not sure how to upgrade from ForgeMultipart-universal 1.0.0.193 to the 249 without crashing all the other mods I have. I would like to know if this ugprade does repair the error and if so how to make it if possible. |
|
My Test server where I'm currently running the updates for my modpack hasn't reported this problem since I started the updates. Unfortunately I was never able to reproduce it 100%, but its been upwards of 4 days with out issues. I don't think anyone can give you a guarantee that its been resolved, but it wont hurt to try. Also, it should just be a matter of replacing the Multipart jar on both client and server sides. You may also need to either replace CodeChickenLib, or delete it and let it redownload so you can get the version it expects. |
|
I added the 249 mod as suggested and deleted the old codechickenlib and it spit out this error and crashed before the minecraft game launched: |
|
Talk to MrTJP about that one |
|
Do you know where would be a good way to contact him? Sorry to be so noob |
|
+1 |
|
Currently getting this issue on our server when I log in or load the offending chunk. It was triggered oddly the first time. I was switching an mfsu from no redstone behavior to emitting when full. This should have caused an update to the red-alloy-wire (which is a multiblock) to update and perhaps triggered the issue. Though, no new blocks were placed within 24 hours of the issue in this chunk. Pretty odd. LOG: http://pastebin.com/UfKzrN6h Forge version 965 MCPC build 251 EDIT: Realized I was on forgeMultipart version 244, upgrading to 250 and trying again. |
|
My apologies. I thought I had already updated Forge Multipart to 1.0.0.250 on this build, I had not. Updated Multipart and the error ceased. |
|
MC 1.7.2 |
|
Getting this on MC 1.6.4, with latest MCPC+ (#270) and FMP #250, on my personal server. Every time I log out and back in, my Mekanism salination plant, which straddles a chunk boundary, was non-functional (not multi-block). I would have to click the button to make it active again. However, after this occurred several times, now every time I clicked the button to re-activate the plant (and become a valid multi-block), the client would crash with this exception. At the same time, a Mekanism elbow-joint pipe connecting to a valve on the planet would be invisible, and when the valve block it attached to was broken, it also crashed the client. Switched to regular Forge, and everything is fine. I can try to put together a ready-to-go package for you to test with if you are still interested, Chicken-Bones. |
|
An update - I was building a pared down version of the server as a test case, and I managed to get into a 100% repro case just loading into a chunk. I've pared the build down to Mekanism, ForgeMultipart, MCPC+, NEI, and a single region file, with a guaranteed crash on approaching certain coordinates. It definitely only happens with MCPC+, though. |
|
Now on my private server, running standard Forge (not MCPC+), my wife and I both experience this crash when dying in the Nether and respawning, in the same area that causes problems with the MCPC+ server under other circumstances. |
|
Additional research on this info has shown that one cause (perhaps not the only one) is the silent (not calling invalidate) removal of the tile entity on the client. Hopefully this can help replicate the issue and isolate causes |
|
It sort of worked for the original crash on connection, but there is now a new crash (this is with MCPC+; I have not tested the change with our non-MCPC+ server when dying in the Nether). I was able to get in and re-activate the device once, then to test I disconnected and tried reconnecting. Now I encounter this new crash on the client with 1.0.1.268: java.lang.NullPointerException |
|
That one I can't help you with, MCPC's got you beat there. |
|
Had that crash without mcpc, happens when I destroy multiparts at the same time or fast |
|
@Keridos |
|
I used the awakened Ichorium pickaxe from Thaumic Tinkerer, do no know how it works internally. |
|
This crash occurring many time for me today. Try reproducing with itemducts, and a combination of hollowed covers and covers. Place them all over, then break them all. |
|
This exact same issue occurred on our CrackPack server running with the latest cauldron. In our case we found the culprit: Flans mod. (Note that this might not be the same for you, but wanted to let you know anyway) A gun was placed, and as soon as you entered loaded the chunk client side, it crashed, but when you then logged back in again it did not happen anymore until the chunk was re-loaded client side. Note that removing the gun fixed the problem. |
|
I'm closing this thread as this specific crash log cannot exist with the latest versions. There are a few remaining cases that I couldn't catch properly, but the majority should have been fixed. Development for 1.6.4 has stopped, please only report issues for the latest 1.7.2/1.7.10 versions |
This is the client crash that will spam when you try to login into a server. It stops if you can manage to tp the person out of the spot they were in before it kicks them. Then once they login again they are fine.
http://pastebin.com/6LXPhBaT
ForgeMultipart-universal-1.6.4-1.0.0.231
The text was updated successfully, but these errors were encountered: