ID:1736720
 
Resolved
BYOND Version:506
Operating System:Ubuntu 14.04, Windows 8.1
Web Browser:Chrome 39.0.2171.71
Applies to:Dream Daemon
Status: Resolved

This issue has been resolved.
Descriptive Problem Summary:
Ubuntu 14.04 Server, BYOND 506.1247
On any player joining a server running a specific branch of Space Station 13, Dream Daemon crashes with an illegal operation.

Windows 8.1, BYOND 506.1247
On server startup running the same branch, Dream Daemon crashes.

Code is at https://github.com/GinjaNinja32/Baystation12/tree/drinks - for any not familiar with GitHub, there is a "Download ZIP" button on the right hand side which will give you a zip file containing the code.

Numbered Steps to Reproduce Problem:
Ubuntu:
1. Host world (code linked above)
2. Join world

Windows:
1. Host world

Code Snippet (if applicable) to Reproduce Problem:
See above.

Expected Results:
Dream Daemon to not crash

Actual Results:
Dream Daemon crashed:
BUG: Crashing due to an illegal operation!
proc name:
source file: combat.dm,5
usr: null
src: Dark Gygax (/obj/mecha/combat/gygax/dark)
call stack:
Dark Gygax (/obj/mecha/combat/gygax/dark): ()

Backtrace for BYOND 506.1247 on Linux:
Generated at Thu Dec 11 03:17:28 2014

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb14]
libbyond.so [0xf72d1000, 0x0], 0x1ed419
[0xf778b000, 0xf778b410], [0xf778b000, 0xf778b410]
libbyond.so [0xf72d1000, 0x0], 0x1ed419
libbyond.so [0xf72d1000, 0x0], 0x2048d2
libbyond.so [0xf72d1000, 0x0], 0x211bb4
libbyond.so [0xf72d1000, 0x0], 0x21defe
libbyond.so [0xf72d1000, 0x0], 0x21e04b
libbyond.so [0xf72d1000, 0x0], 0x1c00c5
libbyond.so [0xf72d1000, 0x0], 0x1bfe6d
libbyond.so [0xf72d1000, 0x0], 0x1bfe6d
libbyond.so [0xf72d1000, 0x0], 0x1c3abd
libbyond.so [0xf72d1000, 0x0], 0x1c8e4e
libbyond.so [0xf72d1000, 0x0], 0x1c9c45
libbyond.so [0xf72d1000, 0x0], 0x1c9fea
libbyond.so [0xf72d1000, 0x0], 0x1e9f05
libbyond.so [0xf72d1000, 0x0], 0x1ebd23
libbyond.so [0xf72d1000, 0x0], 0x1e81d9
libbyond.so [0xf72d1000, 0x0], 0x1e8abc
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ae19]
libc.so.6 0x19990, 0x19a83 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a771]

Recent proc calls:



/proc/islist
/proc/islist
/proc/difflist
/atom/New
/atom/movable/New
/obj/machinery/New
/atom/New
/atom/movable/New



/proc/pick_n_take
/proc/pick_n_take

Does the problem occur:
Every time? Or how often? Every time
In other games? Unknown
In other user accounts? Unknown
On other computers? Definitely happens for at least two different clients, also two different server machines as explained above.

When does the problem NOT occur? When not on the "drinks" branch of my fork (linked above).

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Unknown.

Workarounds:
None known
Quite a few crashes have been fixed since 506.1247, so I would recommend trying that in the newest beta build. It's entirely likely this issue has already been dealt with.
I'll test that, then, and see if it helps.

BYOND 507.1269, same OSes:
Windows:
same issue
Ubuntu:
DreamMaker: symbol lookup error: DreamMaker: undefined symbol: _ZN8ByondLib4InitEiPPc15ByondServerType on attempting to compile
DreamDaemon: symbol lookup error: DreamDaemon: undefined symbol: _ZN8ByondLib4InitEiPPc15ByondServerType on attempting to run

Seems the above is a PATH-related issue. Testing now.
Issue seems fixed in 507.1269 on Linux, still present on Windows. also fixed in Windows after a clean compile.

Issue seems to be restricted to that specific branch compiled on 506.1247, any other branch or 507.1269 work correctly.

How stable are 507.x builds currently? Would it make sense to switch to 507.x as a general-use build now?
They're quite stable. I believe it's likely the issue you ran into was a compiler problem that triggers on certain very large games including many SS13 branches.
In that case, I'll switch to 507.x as general-use. Unless you plan to bugfix 506.x, this issue's probably resolved.
Yeah, we've moved on from 506.
Lummox JR resolved issue