[MC-13386] Regular crashes when in Nether; invalid memory access

Game crashes very frequently while in the Nether. Makes it very hard, nearly impossible, to do anything.

Seems like hitting ESC directly on entry makes the crash a bit rarer, but it's no guarantee the game will continue to run normally.

This does not happen in the Overworld. Idk about the End, haven't been there yet.

Made a crashlog using instructions found at http://www.minecraftwiki.net/wiki/Crash#Mac_OSX

At the moment of the crash, log shows:

10/04/2013 01:41:25 [0x0-0x57c57c].com.Mojang Specifications.Minecraft.Minecraft[49196] Invalid memory access of location 0x7fc0351a7 rip=0x7fc0351a7
10/04/2013 01:41:36 com.apple.launchd[136] ([0x0-0x57c57c].com.Mojang Specifications.Minecraft.Minecraft[49196]) Exited abnormally: Bus error
10/04/2013 01:41:36 com.apple.launchd[136] ([0x0-0x57c57c].com.Mojang Specifications.Minecraft.Minecraft[49196]) Exited abnormally: Bus error

Invalid memory access. Must be a bug.

Rest of the log is fine, nothing unusual there. So no need to attach that. The crash comes out of the blue, with above error messages in Console.

—

I tried searching for this, but all the Nether crash related issues are shut down and none of them speak of invalid memory access. That is why I believe this needs to be a new issue. Thank you.

Linked issues

duplicates 1

MC-2749 Went to nether. Minecraft crashed (Solved by Java update) Resolved

Attachments

crash-2013-04-10_09.03.09-client.txt

nethercrash-13386.txt

Comments 16

Tails 2013-04-10T00:53:02Z

Please attach the crash report, otherwise this ticket is incomplete.

Daedalus Young 2013-04-10T00:55:00Z

There is no crash report, I already pasted the excerpt showing the crash.

Tails 2013-04-10T00:56:18Z

This is a technical support issue; this site is for bug reports only. For technical support please use the Mojang Support Center.

Daedalus Young 2013-04-10T00:57:35Z

This is the only report there is.

Daedalus Young 2013-04-10T00:58:47Z

This is a bug. Game crashes - that is a bug.

6 more comments

Tails 2013-04-10T01:00:01Z

This crash is not caused by Minecraft, thus not a Minecraft bug.

Daedalus Young 2013-04-10T01:00:36Z

Well that's the last time I volunteered in helping make software better.

Daedalus Young 2013-04-10T01:08:33Z

"Something" in the game must trigger that crash however. It is not random, I have never seen it on other Java programs, it happens only in the Nether, is fairly repeatable. If I stay in the Overworld, all is fine, but "something" in the code must trigger something in Java which makes it crash. If that something was not in the game, then it would not crash. So it is caused by something that Minecraft does, otherwise it would be a random Java crash. And it clearly is not.

kumasasa 2013-04-10T05:47:28Z

Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.

Daedalus Young 2013-04-10T08:09:05Z

Sure, I don't think it gives any clues to why the game crashes, as this of course is not the crash itself, but here it is.

I updated lwjgl in the meantime (as suggested on forum, could've just told me here to try that, I know this is not support, but come on, we're not bureaucratic or anything are we?), that did not fix the issue.

kumasasa 2013-04-10T19:22:40Z

The crash report tells a lot:

Java Version: 1.6.0_26, Apple Inc.

Your Java version is out of date. Please update your Java to the latest version: http://www.java.com/en/download/ . Keep in mind that when using a 32-bit browser on a 64-bit OS the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp .

kumasasa 2013-04-10T19:23:14Z

Duplicate of MC-2749

Daedalus Young 2013-04-10T19:48:44Z

I cannot update Java, I already use the latest version that is available for Mac OS X 10.6 and lower.

Daedalus Young 2013-04-11T17:24:13Z

Hah, seems I fixed this issue myself. And looks like it actually is a Minecraft bug after all. But since you didn't even consider the possibility and are merely focused on closing as much issues as you can, marking them as "not our problem", not even interested in attempting to locate the source of the problem, I don't know if I can be bothered making a bug report on the issue.
Congratulations, you succeeded in people not wanting to contribute anymore.

Mustek 2013-04-11T19:23:45Z

> Fixes issue, tells nobody the solution.

Daedalus Young 2013-04-11T20:54:23Z

I told people the solution. Those that were helpful in the first place. Even if their suggestion didn't fix it. They took the time to listen to me and suggest a possible fix, so I repay them by telling how I probably fixed the issue. They didn't just say "not our problem, go away".

Why should I care about filing bug reports if it's all tossed in the bin without being looked at?