CoreProtect

CoreProtect

1M Downloads

Unable to create native thread

asacavanagh opened this issue ยท 3 comments

commented

I'm having a really weird bug with the latest Patreon release of CoreProtect.

When players load a certain section of the world, I'm getting a consistent crash.
This only happens when I have CoreProtect loaded on the server (Using CP 23.1), without it, the server is stable.
Nothing has changed on the host server or docker configurations from 1.20 to 1.21.
I did try removing all my Java Args too, but the issue still persists.

CP22.4 worked fine back in 1.20.X, this is just a recent issue in 1.21.1. I don't recall having an issue with CP23.0 to start with, however I did try to downgrade from 23.1 to 23.0 for testing purposes and now the issue persists with that version as well. I thought it may have been a map issue, but as soon as I remove CP, the crashes stop.

Crash Report: crash-2024-09-08_04.50.06-server.txt
I have also generated a spark heapsummary as Skullians suggested: https://spark.lucko.me/jvqnjNppcJ

I did try to catch a heapsummary when a memory spike was occuring but every time I tried, the summary just reported normal sub 1GB memory usage, which is odd.

commented

Sorry, I should have mentioned, I am using MySQL. However for testing I have changed it to use SQLite and changed to version 22.4.

The same issue is still occuring at this same point in the world and still only while CoreProtect is running.
crash-2024-09-09_01.56.06-server.txt

In my control panel, there is no noticable memory spikes either.
When this report was generated, the control panel was only reporting about 1.46GB of the 20 or so assigned to the server.

commented

Please perform the following:

  1. Stop your server
  2. Rename your database.db file to database-backup.db (assuming you're using SQLite)
  3. Remove CoreProtect v23+, and replace it with CoreProtect v22.4
  4. Start your server, and see if the same issue occurs at that location in the world.

Once complete, you can stop your server, switch back to CoreProtect v23, and rename database-backup.db back to database.db.

Thank you!

commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.