ID:1866413
 
BYOND Version:507
Operating System:Windows 8
Web Browser:Chrome 43.0.2357.81
Applies to:Dream Daemon
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:Game crashes sometimes, when I check nohup.out with logging enabled, i get this:
http://gyazo.com/d183c3f7c4d365583e68414999290c73

Numbered Steps to Reproduce Problem:
Run the game on linux server or whatever


The game does commit a lot to cache if that matters. Such as pngs and some other stuff.

MEGA EDIT: http://puu.sh/idZyp/cd559a3d92.out
Logs uploaded. I'll go through them myself.

Update:
Just spotted that a replica of the .rsc is made and both are capped up.
http://gyazo.com/1a6396e80a4e4b6e5d66deb1c0f88807
Could this be the issue?


Edit
BUG: Crc mismatch in ReadCacheItem
BUG: Finished erasure with refcount=1 (ref=23:15) DM (:65535)
BUG: Crc mismatch in ReadCacheItem
BUG: Crc mismatch in ReadCacheItem

Going through the nohup.out log, I found this admist the spam of Crc mismatch bugs.

and it repeated:
BUG: Crc mismatch in ReadCacheItem
BUG: Finished erasure with refcount=1 (ref=23:2) DM (:65535)
BUG: Finished erasure with refcount=1 (ref=23:1) DM (:65535)
BUG: Finished erasure with refcount=1 (ref=23:0) DM (:65535)
BUG: Unexpected certificate (6)
BUG: Unexpected hub certificate (65535)
BUG: Finished erasure with refcount=1 (ref=23:18) DM (:65535)
BUG: Removing corrupt rsc entry 'Brown Fur3.dmi'
BUG: Removing corrupt rsc entry 'Brown Fur3.dmi'
BUG: Removing corrupt rsc entry 'Brown Fur3.dmi'
BUG: Sequence number D0BC expected but 42 received
BUG: Unexpected hub certificate (5)
BUG: Crc mismatch in ReadCacheItem
BUG: Crc mismatch in ReadCacheItem
BUG: Crc mismatch in ReadCacheItem


Somewhere within the logs:
BUG: Corrupt block header
BUG: Fmem block size at 170 is 0/1348328 with type 6.
BUG: Error reading file memory structureFile offset: 170
Real position: 175/1348328
BUG: Writing invalid root to savefile 'SaveBackup/rakuzumi' (parent=0)
BUG: Writing self-parent to savefile 'SaveBackup/rakuzumi' (id=0)
BUG: Orphan savefile buffer x exported to /home/eots/SaveBackup/rakuzumi_lost.txt
BUG: Orphan savefile buffer y exported to /home/eots/SaveBackup/rakuzumi_lost.txt
BUG: Orphan savefile buffer z exported to /home/eots/SaveBackup/rakuzumi_lost.txt
BUG: Orphan savefile buffer creator exported to /home/eots/SaveBackup/rakuzumi_lost.txt
BUG: Failed to verify file block (fptr = 111, type 1/2, size 54/0, block = 0xbce8904)
BUG: Ccorrupt or invalid savefile 'SaveBackup/rakuzumi'
BUG: Attempting auto-recovery of '/home/eots/SaveBackup/rakuzumi'
BUG: Backed up old savefile as '/home/eots/SaveBackup/rakuzumi_bad_000.sav' and exported text to '/home/eots/SaveBackup/rakuzumi_bad_000.txt'. REMOVE OR RENAME THESE FILES. If too many of these files build up, auto-recovery will be disabled.

These below are all saved in smething caled TechniqueDatabase which is just.. a .sav file
BUG: Removing corrupt rsc entry 'Clay Bird.dmi'
BUG: Removing corrupt rsc entry 'Gabbys c2 dragon.dmi'
BUG: Removing corrupt rsc entry 'C1 Centipede.dmi'
BUG: Removing corrupt rsc entry 'Clay Bird.dmi'




Okay, I'll stop flooding this message and use pastebin after the perhaps most informtive bit:

The BYOND hub reports that port 1338 is reachable.
BUG: Unexpected message 26,67
BUG: Unexpected message 26,51
BUG: Sequence number F6CD expected but 42 received
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 507.1273 on Linux:
Generated at Fri Jan 30 04:09:04 2015

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb74]
libbyond.so [0xb71d0000, 0x0], 0x2927ab
[0xb7703000, 0xb7703600], [0xb7703000, 0xb7703600]
libbyond.so [0xb71d0000, 0x0], 0x2927ab
libbyond.so [0xb71d0000, 0x0], 0x2441f6
libbyond.so [0xb71d0000, 0x0], 0x242547
libbyond.so [0xb71d0000, 0x0], 0x1dd263
libbyond.so [0xb71d0000, 0x0], 0x289a06
libbyond.so [0xb71d0000, 0x0], 0x249ec6
libbyond.so [0xb71d0000, 0x0], 0x2cb88b
libbyond.so [0xb71d0000, 0x0], 0x23e782
libbyond.so [0xb71d0000, 0x0], 0x23fc9b
libbyond.so [0xb71d0000, 0x0], 0x244ff7
libbyond.so [0xb71d0000, 0x0], 0x245739
libbyond.so [0xb71d0000, 0x0], 0x2cc7b5
libbyond.so 0x2ce8f0, 0x2cf06d
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804af24]
libc.so.6 0x16d30, 0x16e16 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a7b1]

Recent proc calls:
/mob/proc/Run
/mob/proc/AutoAFK
/mob/proc/AutoAFK
/mob/proc/AutoAFK
/mob/proc/CliffGain
/mob/proc/WaterGain
/mob/proc/CliffGain
/mob/proc/WaterGain
/mob/proc/CliffGain
/mob/proc/WaterGain
/mob/Stat
/mob/Stat
/mob/Stat
/proc/Months
/proc/Days
/proc/Months

To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1

Fri Jan 30 04:18:03 2015
World opened on network port 1338.
Welcome BYOND! (5.0 Beta Version 507.1273)

Or this code can be embedded:
IFRAME: http://www.byond.com/play/embed/167.114.144.110:1338
That savefile is corrupt. I think you'll have to let that one go. If you're not sure which one it is, try putting in some debugging before loading each savefile.
What about the crashes? That's another thing that's confusing me. IT's been happening on the last and the most recent byond vesions (I updated last night, and the same crash repeated.) Here's a backtace copied straight out of the puu.sh logs.

BUG: Removing corrupt rsc entry 'Sidecut Shirt.dmi'
BUG: Removing corrupt rsc entry 'Sidecut Shirt.dmi'
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 507.1283 on Linux:
Generated at Sat May 30 20:12:06 2015

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb74]
libbyond.so [0xae283000, 0x0], 0x1e671c
[0xae795000, 0xae795410], [0xae795000, 0xae795410]
libbyond.so [0xae283000, 0x0], 0x1e671c
libbyond.so [0xae283000, 0x0], 0x1f0b19
libbyond.so [0xae283000, 0x0], 0x1f1c31
libbyond.so [0xae283000, 0x0], 0x1f734d
libbyond.so 0x303ab0, 0x303bfa
libbyond.so 0x2d2260, 0x2d2462
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804af24]
libc.so.6 0x16d60, 0x16e46 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a7b1]

Recent proc calls:
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/mob/Stat
/proc/Months
/proc/Days

To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1

./host.sh: line 2: -logself: command not found


I don't understand what the illegal operation thing means : (.