The game does work when you use the Linux launcher, as that just runs the system default Java.
It occurs in this (not fully finished) map that I'm working on
I'm guessing that nightly build of LWJGL has been made into a stable release yet, or Mojang has not pushed it to the launcher.
Thanks Tails, will work with atlassian to try to get it fixed.
Updated with new screenshots and affects version number information
not resolved, please re-open. Issue still occurs in launcher version 1.2.
Here is a video that I recorded that demonstrates the issue occurring in different circumstances. I left the activity monitor and console open to show when lag began to occur. https://www.youtube.com/watch?v=8rh-qTdBoY4
Is this in the right project?
same on OS X 10.9 (13A524d) on Minecraft 1.6.2
just put a torch down, not enough light
incomplete, add detail
add a crash log
not helpful, those boxes to type in are there for a reason, add a crash report
It might have been lightning and the fire may have only become visible after a block update.
I have been able to confirm it is MC-17630 in certain circumstances. I think the latest build of Mac OS X 10.9 fixed the problem with the server having problems on peaceful worlds. Here is a screen-recording of the problem: https://www.youtube.com/watch?v=8rh-qTdBoY4
I would say keep all current pistons as BUD pistons. That way nothing breaks. The crafting recipe could just reverse the redstone and iron or just use more redstone for the BUD piston.
This is very weird. I just tried playing on the same world, and the server didnt have any problems. It only sometimes does, but it happens 99% of the time. The Mac OS X 10.9 beta was just updated to build (13A524d) today, so that may have fixed the problem, but I don't know, I will try again tomorrow and see if the problem returns.
Grum, I think we need your input on this issue again. This comment section has just turned into a massive argument over nothing. You said that you would try to put a game rule in, and I think that stirred up commotion. I think the options to resolve this problem are: add a game rule(not optimal), remove the BUD, name it as a feature and disable comments here, make a BUD block, or split the piston into a BUD piston and a non-BUD piston. My opinion lays with the split, but other people may have differing opinions. Love to hear what you think and hope it can resolve some of these arguments.
It is worth noting though, that this occurs on this survival world, "air" maps such as Sethbling's supercraftbros, and super flat worlds, but it takes longer to start lagging on the "air" and super flat worlds.
No that's not the issue. It's a due to Java changing in OS X. I tried it anyways, but that's for people on older OSes.