Crashing on startup on Linux

ID:2405301
 
Oct 14 2018, 1:54 pm
Resolved
In some rare cases, creation of temp files could cause a crash.
BYOND Version:512.1453
Operating System:Linux
Web Browser:Firefox 62.0
Applies to:Dream Daemon
Status: Resolved (512.1454)
This issue has been resolved.
Descriptive Problem Summary:

When compiled in the version 1453, the server experiences an immediate crash on startup when launched on Linux machine [Byondpanel hosting]; After reverting to 1448, server works correctly and it also works correctly in 1453 during local testing on Windows machine.

Server log excerpt:

Sun Oct 14 15:45:03 2018
World opened on network port 34463.
Welcome BYOND! (5.0 Beta Version 512.1453)
The BYOND hub reports that port 34463 is reachable.
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 512.1453 on Linux:
Generated at Sun Oct 14 15:46:17 2018

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bd64]
libc.so.6 [0xb6ccb000, 0x0], 0x7d1a1
 [0xb77a3000, 0xb77a340c], [0xb77a3000, 0xb77a340c]
libc.so.6 [0xb6ccb000, 0x0], 0x7d1a1
libc.so.6 0x7cd80, 0x7cda6 (__strdup)
libbyond.so 0x375500, 0x375528
libbyond.so [0xb71de000, 0x0], 0x364922
libbyond.so [0xb71de000, 0x0], 0x2e13fb
libbyond.so [0xb71de000, 0x0], 0x2040bb
libbyond.so [0xb71de000, 0x0], 0x2497ef
libbyond.so [0xb71de000, 0x0], 0x25f759
libbyond.so [0xb71de000, 0x0], 0x260adf
libbyond.so [0xb71de000, 0x0], 0x2cc8b1
libbyond.so [0xb71de000, 0x0], 0x351648
libbyond.so [0xb71de000, 0x0], 0x352225
libbyond.so 0x353e90, 0x35421b
libbyond.so 0x354350, 0x35455d
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804af94]
libc.so.6 0x19440, 0x19533 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a7d1]

Recent proc calls:
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del
/atom/proc/(init)
/turf/Del


Numbered Steps to Reproduce Problem:

1. Startup server on Byondpanel.
2. After typical load time, it immediatelly crashes.

Code Snippet (if applicable) to Reproduce Problem:

N/A

Expected Results:

Server starting up.

Actual Results:

Crash, creation of core file, in couple of times a corrupted .dmb file was created; two times the hosting server reverted its BYOND version back to 511.

Does the problem occur:
Every time? Or how often? Every time.
In other games? N/A
In other user accounts? N/A
On other computers? Works fine when hosted locally on a Windows machine (due to lack of access to ports it's not a hosting alternative)

When does the problem NOT occur? On version 1448

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) As above

Workarounds: None currently, besides using older version - which is experiencing previously reported issues.

Oct 14 2018, 2:09 pm
Issue was also reported to BP staff due to the odd things happening with BYOND version reverting to 511 upon some of these issues.
Oct 14 2018, 8:09 pm
511 is not a good choice for reversion; I would recommend going back no further than 512.1448. Too many issues have been fixed since 511.
Oct 14 2018, 8:27 pm
Yeah, it seems the issue is on the side of BP autoupdater which keeps trying to revert/change version mid-server run. I think this can be closed.
Oct 14 2018, 8:33 pm
I found what should be causing this issue, and a fix will be available in the next release.
Oct 14 2018, 8:34 pm
Lummox JR resolved issue with message:
In some rare cases, creation of temp files could cause a crash.
Oct 16 2018, 3:14 am
Descriptive Problem Summary:

Pretty shortly into the runtime of the server, another crash occured - not sure if it's the same issue that was already fixed as the error printouts seem slightly different.

Numbered Steps to Reproduce Problem:

1. Start server.
2. Players begin to log back in.
3. Around 10-20 minutes later server crashes, core file generated.

Code Snippet (if applicable) to Reproduce Problem:

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bd64]
libc.so.6 [0xb6c51000, 0x0], 0x7d1a1
 [0xb7729000, 0xb772940c], [0xb7729000, 0xb772940c]
libc.so.6 [0xb6c51000, 0x0], 0x7d1a1
libc.so.6 0x7cd80, 0x7cda6 (__strdup)
libbyond.so 0x375500, 0x375528
libbyond.so [0xb7164000, 0x0], 0x364922
libbyond.so [0xb7164000, 0x0], 0x2e13fb
libbyond.so [0xb7164000, 0x0], 0x2040bb
libbyond.so [0xb7164000, 0x0], 0x2497ef
libbyond.so [0xb7164000, 0x0], 0x25f759
libbyond.so [0xb7164000, 0x0], 0x260adf
libbyond.so [0xb7164000, 0x0], 0x2cc8b1
libbyond.so [0xb7164000, 0x0], 0x351648
libbyond.so [0xb7164000, 0x0], 0x352225
libbyond.so 0x354350, 0x354acd
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804af94]
libc.so.6 0x19440, 0x19533 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a7d1]

Recent proc calls:
/proc/StunImmuneCheck
/proc/StunCheck
/mob/Players/Stat
/mob/proc/HasSSjVars
/mob/proc/TransActive
/mob/proc/HasPassive
/mob/proc/HasKiControl
/mob/proc/HasPassive
/mob/proc/HasMovementMastery
/mob/proc/GetPowerUpRatio
/mob/proc/Update_Stat_Labels
/mob/proc/GainLoop
/mob/proc/HasPassive
/mob/Players/proc/MovementLoop
/mob/proc/HasPassive
/mob/Players/proc/MovementLoop


Expected Results: Server runs.

Actual Results: Server crashes.

Does the problem occur:
Every time? Or how often? Every time
In other games? n/a
In other user accounts? n/a
On other computers? n/a

When does the problem NOT occur? Similar issue was not observed on previous versions

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) 1448

Workarounds:

Oct 16 2018, 9:10 am
In response to Kokutou
Yeah, it's identical, so I'm merging the threads. Take a look at the crash data: there's absolutely no difference in the most recent few addresses (nearest the top).