On 08/09/11 02:11, Chris wrote:
On 9/7/2011 4:34 PM, Justin Clark-Casey wrote:
That's quite odd, since even a deadlock shouldn't freeze the command console.
If you're running on mono, next time that happens you could kill the process
with SIGQUIT, which will dump thread
information to STDOUT (not the OpenSim log). You could then post that in a
Mantis.
Hmm no mono here... running on Windows using .NET largely because of the speed
benefit in compiling scripts. I would
switch my server back to Linux in a heartbeat if Mono could be faster than it
is now =)
I can say that it happens about every 10th login or so and usually after
running the server a few hours. It only happens
when an avatar tries to log in. I haven't experienced any freezes/lockups while
actually logged into the server fully so
far. I've noticed the lockups mainly when there is at least 1 avatar logged
into the server and another is trying to log
in. It is very inconsistent though.
Is there a way to get thread out put on Windows .NET?
I haven't yet done it myself, but there are some instructions at
http://stackoverflow.com/questions/190236/how-do-i-make-a-thread-dump-in-net-a-la-jvm-thread-dumps
--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
