Lighting appears to cause crash

[t2wave]

lastest.log:

lighting bug - Pastebin.com

fml-server-latest.log:

lighting crash fml - Pastebin.com

Crash report:

lighting crash report - Pastebin.com

[simon816]

Looks like the same problem as another thread, try my suggestion from here:

Error SpongeCoremod, I need help

There appears to be an issue with the “async lighting” optimisation patch that sponge has. You can disable the patch under the “optimizations” section, set async-lighting=false I suggest you make a report on the github issues page (https://github.com/SpongePowered/SpongeCommon/issues/new)

[Aaron1011]

The original cause of this crash is due to a tick exceeding 60 seconds, as you can see at the end of latest.log:

[15:33:12] [Server Watchdog/FATAL]: A single server tick took 66.69 seconds (should be max 0.05)
[15:33:12] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.
[15:33:14] [Server Watchdog/ERROR]: This crash report has been saved to: /home2/dc/sponge/./crash-reports/crash-2017-04-01_15.33.14-server.txt

Apparently, Sponge tried to schedule an async lighting task while the shutdown was happening, leading to the misleading crash report. If this issue happens again, I would reccomend using a profiler such as WarmRoast to determine what’s causing the slowdown.