Matthew Salsamendi
Comments
This will happen if the port is closed without sending the clients a disconnect packet first. This isn't really a bug and can occur naturally if the server isn't shut down fully.
This bug was patched in 1.4.1-pre.
Will be closed by a moderator.
This is usually a server bug, but since Minecraft now runs a client-side server in single-player you may be experiencing the same issues. What are your resource utilization counts looking like? (use Taskmanager to check), are you getting FPS lag?
This is not a bug and lacks extreme detail.
This topic will be closed by a moderator. Please give more detail when submitting bug reports or you will no longer be permitted to use the system.
What kind of lag are you experiencing Jacob? Are you getting FPS (generally slow) lag, lag spikes (random frame drops/freezes), or logic lag (chunks not loading, block issues, etc...)
We need more detail if we're going to help you. It could come down to your video card simply not being fast enough to calculate the scene.
The above responses need an answer if we're going to proceed to be able to debug, that being said I will offer some insight.
The reason you're getting an error that would imply that your on a server, is because you actually are! The way Minecraft now works, for consistency, is that it runs a server on your local machine, and then has your client connect to it. That being said the connection lost error usually implies that something went wrong on your computers network adapter, I'm guessing they probably create a local connection only bound to the local box and thus, if your network adapter falls dead, so will your connection to the server.
That may be a start for troubleshooting.
Not a Minecraft issue (despite it lacking optimization), this issue is system dependent and can be caused by several things.
There is a handy mod called Optifine that you might want to check out which changes some Minecraft internals to create a more performance, and feature friendly environmental.
@EvilSeph
Presuming you know this already but FYI:
This issue is caused by an excessive amount of client-side lighting updates due to the amount of light-sources (lava) present in the nether. These updates (one per tick) are causing massive client-side lag during recalculation of lighting. This lag appears as spikes in frame-rate/render time.
There are several client-side mods available that resolve this issue while still keeping the full functionality. If you could look into these and provide a solution that would be awesome. 🙂
This works fine on Windows 7 Ultimate with an Nvidia 560 Ti GPU.
If you're serious on this one you need to provide more details.
Confirmed in 1.4.2 full
Note, only occurs with the specific redstone setup mention above.
This: http://gyazo.com/f0b4a65d2d1d3e8c5becde70b0f11c36.png?1351196072, however, works fine.
Most certainly not a "Buffer Overrun" (what?), but more likely a Buffer Overflow, in which the network adapter refuses to take the connection due to its workload. This happening will always result in in-console errors with raw stack-traces referencing the class that deals with network connections and the fact that a buffer overflow has been thrown on that socket/host.
Besides, not exactly sure how it's possible to force a buffer overflow to all clients and certainly not the server...
The existence of this has yet to be proved. For further testing I can put up a server and have you attempt to lock it up via whatever means you've stated above. I can then examine the exploit and provide a more detailed approach to a solution.
Thanks for bug-testing!
This is a repeatable bug. However, redstone power needs to be from one redstone repeater positioned between both pistons (powers the two pistons at the same time) this will break the pistons on top.