This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
tjstretchalot's profile picture

[CC 1.78, MC 1.8.9] [SMP] Fatal error, display bugs

Started by tjstretchalot, 06 February 2016 - 11:08 PM
tjstretchalot #1
Posted 07 February 2016 - 12:08 AM
VERSION:
ComputerCraft 1.78, Minecraft 1.8.9, Forge 11.15.1.1732
DESCRIPTION:
When I type things, it often doesn't update the screen until I reconnect
EXPECTED RESULT:
Screen is always updated when I type / something is outputted to the terminal
REPRODUCTION STEPS:
Keep typing something on a computer or a turtle for a minute or two.
SCREENSHOT/VIDEO:
https://www.youtube....eature=youtu.be

Also, randomly it crashed. Here's a log:

http://m.uploadedit....54803599414.txt
Edited on 07 February 2016 - 12:56 AM
hugebones #2
Posted 07 February 2016 - 09:22 PM
Also, randomly it crashed. Here's a log:
http://m.uploadedit....54803599414.txt
Your server crashed because it ran out of allocated RAM:

[15:33:39] [Netty Client IO #2/ERROR] [FML/]: There was a critical exception handling a packet on channel CC
java.lang.OutOfMemoryError: Java heap space

At the moment it seems you only have a maximum of 2GB of RAM assigned to Java:
-Xmx2g -Xms1g
Something to do with networking is probably the cause of the crash.

There are a lot of NegativeArrayIndex and IndexOutOfBounds exceptions. Only conclusion I can come to is somewhere in the code that handles network packets, the array size isn't being checked, or when the index is calculated, it's not being check for values less than 0. This then causes the packet not to be dealt with, which means it isn't removed from the heap, then all the network packets get piled up in the heap and GC can't get rid of them, because something is still referencing them in an array (most likely the one that's causing index exceptions). Then your server runs our of memory…

TL;DR: Memory leak in network code.
HPWebcamAble #3
Posted 09 February 2016 - 01:24 AM
Then your server runs our of memory…

Good catch, that explains why the terminal doesn't update.
Dan might want to look into it.

Although I believe it is the client that crashes, not the server.
Edited on 09 February 2016 - 12:24 AM