Oh, I just happened to be running two connections to SAGE.math when it died. One was running the "ssmul-profile" program which you see there. The other was running the program "top", which displays exactly the information you saw in my post. I just took a capture of the information after it froze on my screen (I work in windoze).
I don't know if either dav or burhanud drove sage mad. Although both processes were using a lot of memory, they had been both running stably for a long time. According to the chart, SAGE still had 5g of free memory anyway. I only posted the info in case someone more guru than me could spot a particular process that might have led to the crash, and because I wonder if "nobody" is a real user. The program I was running was writing a file when sage crashed. I did run the program to standard output for some time to check it, before piping it to a file. So I think it was behaving, but one can never know. Bill. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
