Bret Ryder
- brutus_teabags
- brutus_teabags
- Europe/Stockholm
- Yes
- No
MC-112144
I have a number of tools with the Mending enchantment. I have a zombie XP farm. Until the last update (I think, I don't think I used the XP farm during the previous update) when I collected XP with my tool in my hand the tool's durability would increase. This is going very, very slowly at the moment. My XP bar increases at a normal speed but the tool repairing has slowed to a crawl.
I have a diamond pickaxe that has an Efficiency IV and Mending. I have a zombie mob farm which I have used for XP. In the last couple of updates I've found that my pickaxe doesn't repair when I'm collecting XP with the pick in my hand. My XP increases but not the durability of the pickaxe.
Windows 10.
Java 8 - Update 171
Minecraft crashes as the singleplayer world is loading.
I was unable to attach my crash reports because of the following error:
JIRA could not attach the file as there was a missing token. Please try attaching the file again.
Bret Ryder Can you give me the seed and location where you get the crash ?
In 18w22c I no longer experience a game crash when I (re)test these commented on seeds:
8223045022386406090 commented on by Meri Diana and Xavom
-7269461605076408993 commented on by greener.ca
-6968998364217797098 commented on by Bret Ryder at/near chunk 55,71
The 3rd on the list, I approached said chunk from 4 directions each in different tests. I also launched the game with default JVM arguments, and using -Xmx3G (memory bug: MC-121318).
Bret Ryder I have experienced that same game stutter near chunk 55,71 only when using the default JVM arguments.
You had commented crashing "chunk 55, 71 (multiple times) and chunk 57, 71 (once)".
In your latest comment you were nowhere near that point when it crashed. I have retested both of these areas and have not experienced any issue.
Perhaps it would be helpful if you provide that crash report and/or retest that seed/areas and report back providing that crash report. There is a frozen ocean next to 3,55. Some of the crashes I've experienced in the past happened near this biome type.
Bret Ryder I tried several more times using the info in your crash report. The crash location was about 651, 64, 1054. I even tried your JVM arguments. The only time I experienced anything (100% memory stops/starts) was when I created the world in 1.12.2 first, then loaded in 18w22c using default JVM's . But still no crash.
Could the issue here be that your world was generated in a previous snapshot?
Have or can you generate from 18w22c and head to the crash site?
Don't see my duplicated comments here but game crashes when I explore in one particular direction although the chunk where the game crashes varies. I have numerous bug reports if they are any use. This occurs on 18w22b and the previous snapshot as well. As I was playing in snapshots I am unable to utilise any of the usual methods of fixing my world.
@ProfMobius (Thomas Guimbretiere) My seed is -6968998364217797098.
The locations are as follows...
chunk 55, 71 (multiple times) and chunk 57, 71 (once).
Hope that is useful.
I ran another test this morning. A couple of things. First When I head in the direction of 55,71 I experience a lot of jerky gameplay almost like my powerful laptop is struggling but the debug screen reveals that barely 13% memory is being used, this has happened every time I've encountered this problem. Secondly, although the bug report I got this morning mentions a problem with 55,71 I was nowhere near that point when the game crashed. I can't remember exactly where I was but it was something like 36,65.
@Xavom
crash-2018-06-01_09.14.53-server.txt
As I said the report says that the game crashed whilst generating 55, 71 but although I was heading in that direction I wasn't near to that chunk.
I ran the experiment.Started new world using my seed. Made my to the crash point - 55, 71. The game still definitely became more laggy but there was no crash.
I started my original world in a snapshot but I can't remember which one but it wasn't the latest one or perhaps even the one or two before that.
Tested again this morning. I still experience exactly the same lagging and crashes with 22c as I did with previous snapshots.
What I'd really like to know is, is there anything I can do about it? Will the full 1.13 update fix this? is my world just corrupted beyond repair? I'm not really clear on where I go from here. Is this problem that I'm having being worked on?
Thanks for any help you guys can give.
A crash did not occur.
I apologise, I was in a hurry.
I have a number of tools with the Mending enchantment. I have a zombie XP farm. Until the last update (I think, I don't think I used the XP farm during the previous update) when I collected XP with my tool in my hand the tool's durability would increase. This is going very, very slowly at the moment. My XP bar increases at a normal speed but the tool repairing has slowed to a crawl.
Okay, that explains it. Could I make the suggestion that that is maybe changed in the future. Thanks for your help.
Me too.
Masses of mobs spawning in broad daylight at around Y:64. Bats also fluttering all over the place.
I tried to run Minecraft this morning and it started updating the installer. During the update the game crashes and tells me I'm missing some .dlls
I've reinstalled C++, restarted multiple times, repaired Minecraft and uninstalled and reinstalled Minecraft but so far nothing's worked.
@yusufulus
MCL-17664does not describe my problem. Should I start a new thread?What do you mean?
I was playing Minecraft fine last night. The problem only started when I launched MC this morning and it started doing a Launcher update.
I'm not the only one having this problem so it seems. Technical problem or not we could do with some help.
Same problem. Sent here by a rather rude mod.