Descriptive Problem Summary:
Numbered Steps to Reproduce Problem: Start up the game, let it run for like five to ten hours averaging around 40-60 players.
Code Snippet (if applicable) to Reproduce Problem:
Expected Results: The server should run perfectly fine provided the CPU stays stable (which would be anything below 90% for us).
Actual Results: Despite the server's connection and CPU not having any issues, DreamDaemon will crash after around a day or so of activity. Sometimes less. It's really hard to predict when the crashes happen.
Does the problem occur:
Every time? Or how often? Around every day.
On other computers? We've tried to host the game on another machine, and it seems to crash consistently, so something in the code itself might be causing the crash. However, DreamDaemon shouldn't be crashing at all.
When does the problem NOT occur? Never.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Not really.
Workarounds: None.
ID:1292048
 Jun 13 2013, 4:59 pm
|
|||||||||||||
| |||||||||||||
|
Jun 13 2013, 5:07 pm
|
|
Writing A New One
 |
We're going to run the server with -trace and post the logs here once a crash occurs.
|
Consider the steps here: ID:103269 as far as dumping core.
Also, the issue in that case was due to a huge recursion with world.loop_checks=0, so you might want to see if you have that set that way as well. DD should never crash, although without loop checking it is possible due to running out of stack. Of course, we could also have some bugs. | |
We actually do not set world.loop_checks to 0 anywhere in the code, so I doubt that is the issue.
However, are getting some weird error reports on certain savefiles in the game: BYOND Error:(sfile.cpp,1138) failed to open file: I suspect it may have something to do with this, but I can't be 100% sure. | |
Hazordhu randomly experiences immense lag and 100% CPU after some time, too, but I expect it's from crappy 5-year-old code. I do use while() for loops, though.
I've seen sfile.cpp errors, too. And a bunch of the recently fixed refcount BUGs. | |
Tom wrote:
Consider the steps here: ID:103269 as far as dumping core. We're already dumping the core, so we can rule this out. Also, the server is being hosted on 496.1138. We're hesitant to update due to these issues: http://www.byond.com/forum/?post=1291238 If we can get confirmation that they're no longer a problem in the latest version, then we'll go ahead and update. | |
Well if you are dumping core, that means we can probably debug DD itself. We can't do it if you are on an old build though, so we'll have to wait for the update. There are some steps there that elude me at this time but we'll take a look if you continue to get crashes on the latest.
The issue with the hub connectivity is resolved in 1193 (we were simply pointing users to the beta test hub, which is no longer running-- I had forgotten that affected hosting too). I don't know about those other things since no bug reports with any info were filed, but very little has changed in the server so I doubt it's a problem. Also, some of the refcount stuff should be fixed in the latest linux builds (actually not fixed on windows yet because we haven't released it). | |
Okay, thanks, then we'll update. If you want to debug the DD we should be good to go ahead and do that? I'll e-mail you the files if so.
| |
Well, run with the latest and let us know if it crashes and you get a core file.
| |
Okay, sure thing--thanks for the help.
| |
Tom wrote:
Well, run with the latest and let us know if it crashes and you get a core file. Am I correct to say the core gets dumped in the same folder as the rsc and dmb? | |
I'm not sure how Linux works, but I think Hazordhu's hosted on one. It's possible the code is causing random freezes, but as far as I can tell from the log, there aren't any runtime errors or any "suppressing runtime errors" messages. Using the "top" command in PuTTY (I don't completely know what I'm doing, with that), it shows Dream Daemon at 100% CPU and the game is frozen. I'm not sure if that counts as "crashing", since I have to "kill" it manually and start it back up.
Sometimes, after a while, Hazordhu's framerate gets chopped in half and becomes very slow. Sometimes, it just freezes without warning. I wonder if it's an issue with the host. | |
Kaiochao wrote:
it shows Dream Daemon at 100% CPU and the game is frozen. I'm not sure if that counts as "crashing", since I have to "kill" it manually and start it back up. You've described my issue here. | |
Tom wrote:
Well, run with the latest and let us know if it crashes and you get a core file. A crash occurred, despite updating. What is the name of the 'core file'? Our crashing also seems to be similar to Murrawhip's and Kaiochao's (?): http://www.byond.com/forum/?post=1264881#comment4924862 | |
Well, this is a first. Previously, Dream Daemon would only freeze. This time, it just instantly crashed. I'm not sure what to say about the call stack.
{" The line it points to is just ..() in mob/Del(). The core file is 74,628 KiB. Should I send that? No one's really enjoying the rollbacks caused by these extremely random and unpredictable crashes. | |
Hold onto those files and we'll get you help early this week.
| |
Okay, Tom. Let me know what to do when you find the time.
| |