This is a short one. I do not know if this was lag or a glitch but I decided to report anyway! So, as in my other report, I was far from the spawn in my new found location to build a house and as I was building the floor, which was wooden planks, 3 blocks wouldn't render for about 5 seconds until I placed the fourth. They still lit up when I hovered my cursor over them but it looked just like air. As with my other issue, I did search before reporting so it is not my fault if it is a duplicate issue.
Comments 5
Was fixed at one point but 1.4.2 seriously bad because it has such memory issues - you can sometimes wait ages now for the blocks placed to render but considering I now get a wait bar when trying to open a chest this memory problem is minor. Not resolved but just another memory/performance issue.
Mega spud.. this another that has been closed prematurely. Possibly should be linked to the later bugs re memory especially near water but should not be closed as cannot be reproduced. Probably fixed at one time but memory issues is causing it to happen again.
Don't assume this problem is the same as the later bugs just because they sound similar. If it was, why did literally nobody else report it until 1.2? If it was the same bug, we should have seen many more reports of it on 1.1.
We usually don't combine bugs just because their symptoms sound similar. If we did, we'd run the risk of hiding one bug behind another. Then, when the fix for that one doesn't fix this one, we've lost a lot of time that somebody could have been working on this one, maybe even solved it earlier.
For that matter, who knows if this was even a bug? The reporter himself admitted it might just be lag. For all we know, he was playing Minecraft while leaving a bunch of hoggy apps running in the background, or his device may have been overheating or malfunctioning. About 1/3 of reported bugs aren't actually bugs at all.
Since there's no reliable evidence that anybody else had this problem, and we were not able to reproduce it, and the only person it affected is no longer responding to prompts for more information, and we can't even be sure there was ever a bug here in the first place, closing this ticket as "Cannot Reproduce" is the only sensible thing to do.
Auldrick. You are absolutely right on one score but I would say don't just assume the issue cannot be reproduced just because no-one from Mojang side commented on the call or no other players made a comment. This time I voted for it, started viewing it and was waiting for a response but it was then just closed with no opportunity to say whether the issue still exists.More than one call I was viewing and waiting for an answer on has been closed recently as cannot reproduce when the issue clearly still exists. Therefore, new issues for the same original problem had to be opened. If anyone analyses the stats then the answers are not accurate as 2 calls had been opened for the same issue because one was prematurely closed. On older calls cannot the status be set to awaiting response first and if no response within a certain time scale then set to cannot reproduce or another, more appropriate, closure reason? That way the people who are interested can update the issue and the issue properly kept open, or closed with possibly a more appropriate closure reason, as the case may be.
Cleaning up old tickets: This ticket has not been updated recently (1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki