Why does the lock object have to be static?

by

It isn’t “very common to use a private static readonly object for locking in multi threading” – rather, it is common to use a lock at the appropriate / chosen granularity. Sometimes that is static. More often, IMO, it isn’t – but is instance based.

The main time you see a static lock is for a global cache, or for deferred loading of global data / singletons. And in the latter, there are better ways of doing it anyway.

So it really depends: how is Locker used in your scenario? Is it protecting something that is itself static? If so, the lock should be static. If it is protecting something that is instance based, then IMO the lock should also be instance based.

More Related Contents:

  1. Why is lock(this) {…} bad?
  2. Volatile vs. Interlocked vs. lock
  3. Concurrent HashSet in .NET Framework?
  4. Asynchronous locking based on a key
  5. Re-entrant locks in C#
  6. Is Task.Factory.StartNew() guaranteed to use another thread than the calling thread?
  7. Is it OK to use a string as a lock object?
  8. Does a locked object stay locked if an exception occurs inside it?
  9. How expensive is the lock statement?
  10. Monitor vs lock
  11. lock keyword in C#
  12. What are the differences between various threading synchronization options in C#?
  13. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  14. C# manual lock/unlock
  15. Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
  16. When is ReaderWriterLockSlim better than a simple lock?
  17. Cross-Process Locking in C#
  18. Why is it a bad practice to lock the object we are going to change?
  19. Guidelines of when to use locking
  20. How do I update an ObservableCollection via a worker thread?
  21. Question about terminating a thread cleanly in .NET
  22. Trying to run multiple HTTP requests in parallel, but being limited by Windows (registry)
  23. Thread.Sleep for less than 1 millisecond
  24. What is the impact of Thread.Sleep(1) in C#?
  25. The current SynchronizationContext may not be used as a TaskScheduler
  26. c# working with Entity Framework in a multi threaded server
  27. Thread safe collections in .NET
  28. Invalid cross-thread access issue
  29. increment a count value outside parallel.foreach scope
  30. Async and Await with For Loop [duplicate]

Leave a Comment