[SPIGOT-1093] 1.8.8 Spigot Server crashes after 18hours of Uptime- Optimized and adjusted RAM, still crashing. Please help me find the error! Created: 30/Jul/15  Updated: 31/Jul/15  Resolved: 31/Jul/15

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

Type: Bug Priority: Minor
Reporter: Trevor Nishimori Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: 1.8.7, bug, crash, error, spigot
Environment:

64bit Operating system, Windows Server 2012 R2, 4-Core CPU with 8GB of RAM,


Issue Links:
Cloners
is cloned by SPIGOT-1096 CLONE - 1.8.8 Spigot Server crashes a... Closed
Duplicate
is duplicated by SPIGOT-1096 CLONE - 1.8.8 Spigot Server crashes a... Closed

 Description   

I am running the latest version of Spigot from the BuildTools and my server has been crashing even on 1.8.7 and on 1.8.8 Spigot. I have tried looking up reasons for the crashes and could not find a working solution, I have also tried optimizing my server according to threads on the Spigot forums but still no avail. My server is running 6GB of Ram on a Virtual Dedicated Server from NFOServers.

Here is the pastebin of the error message that shows up when the server stops:
http://pastebin.com/t9h07Gvt

My Start.bat code is:

@ECHO OFF
java -Xms3G -Xmx6G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing -XX:+CMSParallelRemarkEnabled -XX:MaxGCPauseMillis=30 -XX:TargetSurvivorRatio=90 -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -XX:+UseBiasedLocking -jar spigot.jar
PAUSE

Sorry if something on here is wrong as this is the first time i've posted a issue on Spigot.



 Comments   
Comment by md_5 [ 31/Jul/15 ]

I don't believe there is anything wrong here since it's simply checking the session lock. If it happens again post a new report.

Comment by SpigotMC [ 30/Jul/15 ]

Your build is not the latest and therefore may be the reason you are having this issue. Spigot is 1 version(s) behind. CraftBukkit is 1 version(s) behind. This message was automatically generated and is not guaranteed to be a solution to your issue.

Generated at Fri Apr 11 15:29:54 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.