Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server thread dump #227

Open
Kbryst opened this issue Mar 29, 2019 · 7 comments
Open

Server thread dump #227

Kbryst opened this issue Mar 29, 2019 · 7 comments

Comments

@Kbryst
Copy link

Kbryst commented Mar 29, 2019

https://pastebin.com/6WQ8EDn4

Setting this up on 1.13.2
Paper Spigot - 597 (currently latest version)

I'm just doing this on a small test server off my pc before moving it to an actual production server. Just wanted to know if this is an error because this is just a small test server, or can this be something that may show up on my main server?

@ProgrammerDan
Copy link
Collaborator

ProgrammerDan commented Mar 29, 2019 via email

@Kbryst
Copy link
Author

Kbryst commented Mar 29, 2019

I went ahead and to changed this in the paper.yml:
async-chunks:
enable: false
generation: false
thread-per-world-generation: false
load-threads: -1

I am still able to recreate the error

@ProgrammerDan
Copy link
Collaborator

ProgrammerDan commented Mar 29, 2019 via email

@Kbryst
Copy link
Author

Kbryst commented Mar 29, 2019

Sure thing.

So I'm just on a test server, I noticed a first join it popped up (only on the first join).

I'm also testing an /rtp plugin so every time I use it the error shows up again. It looks like its just happening in new chunks to the plugin.

First join log:
https://pastebin.com/E6CVT6N2

Orebfuscator config:
https://pastebin.com/mUvWVN4V
*Its mostly the default config.

Testing with using /rtp:
https://pastebin.com/7D8v9GVD

Edit: First join was not on the latest paper spigot, but the testing with /rtp is on the latest paper spigot.

@ProgrammerDan
Copy link
Collaborator

ProgrammerDan commented Mar 29, 2019 via email

@Kbryst
Copy link
Author

Kbryst commented Mar 29, 2019

Yeah I have no idea either. My first thought was maybe it was 1.12 map rolling to 1.13, but I realize one of the maps that I was on and testing was a brand new map made today.

@ProgrammerDan
Copy link
Collaborator

ProgrammerDan commented Mar 29, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants