Deadlock detected, aborting the server (build id: #396)

[Woazboat]

Could you post your executable as well please. Analyzing a core dump without the corresponding executable sadly isn't possible.

[Seadragon91]

You could also follow the steps here, follow step "Post-mortem analysis"
https://forum.cuberite.org/thread-631.html

[xoft]

@Woazboat He's using official builds from Jenkins, according to the logs, so you could just grab the executable there.

[TheSnowman]

Yes it's an official buil dfrom Jenkins, 2 or 3 weeks old.
Nevertheless, I've uploaded the Cuberite executable (I'm using) in a 7-Zip File in my Google Drive:

https://drive.google.com/open?id=0BzEt4q...TVNeVEzZmM

I've tried to reproduce the deadlock, but I can't identify, which action the really cause is.
Sometimes it's flying, sometimes it's logging in very often, sometimes it seems like it is to mine blocks very fast and sometimes "nothing" happens which causes the deadlock!?

One Question: what would happen, if I disable "Deadlock" in the settings.ini?

Thanks a lot for your help.

[xoft]

If you disable the deadlock detector in the settings, the server will not crash as such, but it will most likely become unresponsive, you couldn't log in, or blocks you place will not get saved into the world.