[Mono-list] strategies for tracking down a run away thread

Sean Dague sean at dague.net
Fri Apr 18 07:35:57 EDT 2008

We've had a subtle bug creep into the OpenSim project where after some
time one thread starts taking 100% of the CPU.  (using ps -eLf confirms
that it's just one thread).  This is one thread out of ~ 100.

While I can use kill -QUIT on the mono process to get thread stack
traces, I still haven't figured out a direct corolation between Linux
LWPs and Mono thread ids.  And nothing in the stack traces has jumped
out as suspicious.

This is all on mono 1.9 (built from source) on Ubuntu 8.04 and 7.10.

Any strategies for doing corrolation between system light weight
processes and mono threads would be highly appreciated, or any other way
to help get to the bottom of our bug.

Thanks in advance,



Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.ximian.com/pipermail/mono-list/attachments/20080418/e52138d7/attachment.bin 

More information about the Mono-list mailing list