I ran some tests of my own and ran in to no issues aside from one of my worlds apparently being corrupt.
Debian 9, amd64, 5GB server RAM
openjdk version 1.8.0_181
openJDK Runtime Environment
openJDK 64-bit Server VM
Attached are files of interest.
latest.log is from an import of a 1.13.2 world (no issues).
2018-12-05-2.log is a brand spanking new world
2018-12-05-2.log is an import from 1.12.2, however I have reason to believe the world is corrupted and therefore the crash report irrelevant to this issue.
mcstart.sh is the script I use to start/stop/manage my MC server(s) (included in case there may be something of interest that I need to change to reproduce).
Fibro, could you provide more info? Do you know how to replicate this issue on a fresh world?
Joseph A Nagy Jr
I ran some tests of my own and ran in to no issues aside from one of my worlds apparently being corrupt.
Debian 9, amd64, 5GB server RAM
openjdk version 1.8.0_181
openJDK Runtime Environment
openJDK 64-bit Server VM
Attached are files of interest.
latest.log is from an import of a 1.13.2 world (no issues).
2018-12-05-2.log is a brand spanking new world
2018-12-05-2.log is an import from 1.12.2, however I have reason to believe the world is corrupted and therefore the crash report irrelevant to this issue.
mcstart.sh is the script I use to start/stop/manage my MC server(s) (included in case there may be something of interest that I need to change to reproduce).
Fibro, could you provide more info? Do you know how to replicate this issue on a fresh world?