Hi Kris-
We haven't seen or heard of this behavior previously. Bob has been trying replicate the problem on OS X with the sleep timer set to 1 minute. He tried several different things in the sessions, such as working with multiple tabs/windows and having long loops playing, but he's been unable to get the problem to occur.
We will get the programmer's thoughts on this shortly, but for now we had a couple of questions:
What version of OS X are you using? Is there any more information with the error, such as a log? Can you send your mcidasv.log file from a session that ended unexpectedly to us? If your logging isn't set to TRACE (from the Advanced Preferences) then set at that level. The next time the session crashes, send us the log file. Any log files elsewhere such as your McIDAS-V or McIDAS-V-System directories?
It's possible that something is being written to the log. Let us know when you get a chance to send them and we'll take a look. If we get any other ideas from the programmers, we'll pass those along as well.
Thanks, Jay
|