Re-entrant locks in C#

by

No, not as long as you are locking on the same object. The recursive code effectively already has the lock and so can continue unhindered.

lock(object) {...} is shorthand for using the Monitor class. As Marc points out, Monitor allows re-entrancy, so repeated attempts to lock on an object on which the current thread already has a lock will work just fine.

If you start locking on different objects, that’s when you have to be careful. Pay particular attention to:

  • Always acquire locks on a given number of objects in the same sequence.
  • Always release locks in the reverse sequence to how you acquire them.

If you break either of these rules you’re pretty much guaranteed to get deadlock issues at some point.

Here is one good webpage describing thread synchronisation in .NET: http://dotnetdebug.net/2005/07/20/monitor-class-avoiding-deadlocks/

Also, lock on as few objects at a time as possible. Consider applying coarse-grained locks where possible. The idea being that if you can write your code such that there is an object graph and you can acquire locks on the root of that object graph, then do so. This means you have one lock on that root object and therefore don’t have to worry so much about the sequence in which you acquire/release locks.

(One further note, your example isn’t technically recursive. For it to be recursive, Bar() would have to call itself, typically as part of an iteration.)

More Related Contents:

  1. Is it OK to use a string as a lock object?
  2. Does a locked object stay locked if an exception occurs inside it?
  3. How expensive is the lock statement?
  4. Monitor vs lock
  5. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  6. .NET 4.0 and the dreaded OnUserPreferenceChanged Hang
  7. When is ReaderWriterLockSlim better than a simple lock?
  8. Create Dynamic Threads in c# [closed]
  9. How do I abort/cancel TPL Tasks?
  10. Cross-thread operation not valid [duplicate]
  11. Concurrent HashSet in .NET Framework?
  12. BackgroundWorker RunWorkerCompleted Event
  13. How do I run a simple bit of code in a new thread?
  14. How to wait for a BackgroundWorker to cancel?
  15. Updating an ObservableCollection in a separate thread
  16. ConfigureAwait pushes the continuation to a pool thread
  17. Unable to use more than one processor group for my threads in a C# app
  18. Why does this simple .NET console app have so many threads?
  19. lowering priority of Task.Factory.StartNew thread
  20. How to catch exceptions from a ThreadPool.QueueUserWorkItem?
  21. Creating threads – Task.Factory.StartNew vs new Thread()
  22. C#/.NET analysis tool to find race conditions/deadlocks
  23. C# manual lock/unlock
  24. How to make make a .NET COM object apartment-threaded?
  25. Show Loading animation during loading data in other thread
  26. C# Windows Forms Application – Updating GUI from another thread AND class?
  27. Thread Safe Properties in C#
  28. Why is it a bad practice to lock the object we are going to change?
  29. Starting a new thread in a foreach loop
  30. Multithreaded NamePipeServer in C#

Leave a Comment