mojira.dev

adsfasdf

Assigned

No issues.

Reported

MC-88514 Display resolution not recognized on 5K iMac Duplicate MC-41269 /gam does not properly complete Duplicate MC-41268 Spread Players spreading to Y 257 Incomplete MC-27740 Minecraft View is Scrolled in Mac OS Duplicate MCPE-4785 Bug reporter fails to scroll on iOS 7 Invalid MC-25523 Minecraft memory leak Invalid MC-22699 Too many output-client.log files Duplicate MC-22688 Minecraft Server Performance Degrades Severely Over Time Duplicate MC-22676 /spreadplayers does not work in nether or when solid block above desired teleport location Incomplete MC-19972 LWJGL spaz Incomplete MC-19955 Baby Cows Everywhere! Duplicate MC-17612 Minecraft does not support app nap Invalid MC-16882 Unable to join LAN or server Duplicate MC-15796 Hopper mine carts not function under certain circumstances Incomplete MC-15715 Sound resets to 27% Fixed MC-10092 Dropped items in creative disappear Duplicate MC-10091 Daylight Sensor fails to update on map close/open Duplicate MC-5831 Redstone torches do not break in 13w01a Duplicate

Comments

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.

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

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.

The world was generated in 1.3, and as such is very large. Even after using a zip, it is still 114MB. This is too large to upload, so I had to upload to Google Drive. Here is the link to that: https://docs.google.com/file/d/0B0C5g0mLYXUDMlBZSk9QaXNuVDA/edit?usp=sharing

The main reason I'm think it's not zombies though is because it occurs on peaceful mode too. Also, the server is playable on for about 5 minutes after launch. Then block lag starts. Then at about 10 minutes of play time in, time outs occur like there's no tomorrow. The can't keep up messages also seem to increase in frequency.

It is over time, the performance is perfect when it starts up, but then just goes downhill from there. Look at the server log I attached and note the time stamps of the server can't keep up messages.

I just launched it with those settings, but it had the same result. I can't remember which version this started occurring on, but i think it was a around the second snapshot. My friend (windows) has been having the same issue, so I don't think it's mac but I very well could be wrong.