• State Not Answered
  • Date
    jon weir
  • Date
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 215 views
  • Users 0 members are here

Bug Report: Full System Crash b2773

6/14/10
V3.1.6 b.2773
1 - Hog 3
1 - Mini Wing
1 - DP8K
1 - DP2K
ESP Vision

Issue - During my normal saving process I generally check the integrity of things to clean up any garbage that has accumulated. This time, when I did that, the server immediately crashed (as evidenced by Vision) Oppening the process window shows everything still running. However, once I killed the server, all the other items (playback, launcher, desktop, etc) went to their not running status. I was able to kill each individual process, but none would restart. I tried shutting down the console, but it was locked. I then killed the desktop, and this took out the process window as well. Hand to pull power and wait for it to drain the battery in order to restart the desk.

Related - This is the second major crash today. The first happened while selecting content. Nothing taxing to the system. Just using 11 layers to view things. This crash took out everything and also gave a stack trace that was the entire screen. This particular crash has happened several times over the past few days of programming.
Parents
  • 0
    I've been able to check integrity on this show file without the crash. Are you still having trouble checking integrity?

    Here is what development said about the stack trace:
    "It happens when a launched process (critical in this case) can’t find itself in the PhysicalNode array. This technically shouldn’t be possible, which is why it’s a trap condition. If it’s at all reproducable, that would be great, else it will be impossible to track down."

    With that said I am going to do a little programming on your show this afternoon and see if I can reproduce the error.
Reply
  • 0
    I've been able to check integrity on this show file without the crash. Are you still having trouble checking integrity?

    Here is what development said about the stack trace:
    "It happens when a launched process (critical in this case) can’t find itself in the PhysicalNode array. This technically shouldn’t be possible, which is why it’s a trap condition. If it’s at all reproducable, that would be great, else it will be impossible to track down."

    With that said I am going to do a little programming on your show this afternoon and see if I can reproduce the error.
Children
No Data
Related

www.etcconnect.com