[SPIGOT-3993] Server stopped responding after server crashed repeatedly on startup Created: 11/Jul/18  Updated: 11/Jul/18  Resolved: 11/Jul/18

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Alex Munoz Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: 1.8.8, crash, error, spigot
Environment:

2560 mb of RAM, hosted online, about 20 plugins in all, EssentialsX included.


Attachments: Text File crash-2018-07-10_20.57.26-server.txt     Text File crash-2018-07-10_20.57.39-server.txt     Text File crash-2018-07-10_21.16.49-server.txt     Text File crash-2018-07-10_21.17.02-server.txt    
Version: 1.8.8

 Description   

The server seems to run fine when it's online, no lag or anything, and /gc reported about a 19.95 - 20 TPS, But when I restart it, especially after editing something in one of the plugin files, it repeatedly crashes on startup with this error:

10.07 21:17:15 [Server] WARN Exception in thread "Craft Scheduler Thread - 3"
10.07 21:17:15 [Server] WARN java.lang.OutOfMemoryError: unable to create new native thread
10.07 21:17:15 [Server] WARN at java.lang.Thread.start0(Native Method)
10.07 21:17:15 [Server] WARN at java.lang.Thread.start(Thread.java:717)
10.07 21:17:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957)
10.07 21:17:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1025)
10.07 21:17:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10.07 21:17:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
10.07 21:17:15 [Server] WARN at java.lang.Thread.run(Thread.java:748)

Then the server stopped responding, here's the console dump:
https://pastebin.com/LarKUdKm

I've also attached some of the crash reports as well.



 Comments   
Comment by md_5 [ 11/Jul/18 ]

1.8 is not supported. Update to 1.12.2

Generated at Tue Apr 15 09:42:02 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.