Problem description:
While hosting, I noticed the Dream Daemon was spinning away at 50%. I stopped hosting and it was still eating up CPU and I'm not sure why. How should I troubleshoot this?
I profiled my app while it was running but I had 0 entries. My app is mostly state based (not a lot going on unless a user does something) so I don't think it was my code that caused the problem.
ts
ID:139734
Sep 10 2010, 1:18 pm
|
|
Sep 10 2010, 9:36 pm
|
|
So.. it happened again and this time it crashed after a minute of high CPU. Not sure what to do with it. I can report it as a bug but I have nothing to offer in the way of details. Seems to happen after the server has been running for a couple hours.
|
In response to Tsfreaks
|
|
Have you tried to profile the world?
If so, what are the results? Are you saving a basic log of what's going on? You could find that there is always a single entry point before the crash, which would be a valuable debugging information. |
In response to Schnitzelnagler
|
|
The profiler shows nothing during that time. When I close the "world", the CPU is still pegged (50%).
The world is state based so absolutely nothing was going on the first time it hung. Its DreamDaemon that is crashing vs DreamSeeker. ts |
In response to Schnitzelnagler
|
|
Dream Daemon is still consistently crashing after a few hours of running. No idea why at this point. Any more suggestions on trouble shooting.
Nothing shows up in any logs. Users were idle this last time around. ts |