Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-71611

Entities causing severe stress on server and client

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.8
    • None
    • Unconfirmed

      Once the game reaches 150+ entities the game begins to cause loads of stress on the computer. On better computers the count may be more, but if on a server its terrible. The new server running thingy seems to be very finicky on this new patch. Meaning things like small amounts of animals can cause massive crashes and massive lag spikes. On previous versions(Just so you don't think its a bad computer) the lag wouldn't come to my untill around 250 AND EVEN THEN it would cause the super crash. Just so you know I've run a server since 1.6 Beta. When playing my new world on 1.8 on my server it began to give everyone the io.netty.handler blah blah error. Then when they log in, 30 seconds after being frozen you get crashed with that error. The server shows ABSOLUTELY NO SIGN of lag. WHAT? WHY? I can't figure that out. But if you relog into the server and your player "is still in the game?" the server has a FATAL crash that is like 100 lines a second of some repeating io.netty.handler blah blah blah crash. Spending countless hours I decided to take it on in game. After watching a video of one of my fav youtubers(dcom77) he said that the mindcrack server was lagging due to entity count. So, I went in game after thinking it was a corrupt chunk I realized the server only locked when I looked at the sheep of 100+. So to test the theory, before I was kicked I walked out of the way for entity rendering on the screen and relogged. NO crash at ALL. So I killed all of them except 6 and the server works again. This is NOT a dupe of that other io.netty.handler.timeoutexception thingy that is not fixed.

            Unassigned Unassigned
            superzippy123 Zippy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: