Lock(object) and ThreadAbortException

posted by  mneon (8)  12 months ago (blogs.msdn.com)

We have experience some weird deadlock using managed code.

We have a class with some shared resources. To protect the shared resources, we create a synchronization object, and use Lock(object) prior to access the shared resources. There is no nested lock so in theory we should never have deadlock.