Using string as a lock to do thread synchronization

by

Strings like that (from the code) could be “interned“. This means all instances of “ABC” point to the same object. Even across AppDomains you can point to the same object (thx Steven for the tip).

If you have a lot of string-mutexes, from different locations, but with the same text, they could all lock on the same object.

The intern pool conserves string storage. If you assign a literal string constant to several variables, each variable is set to reference the same constant in the intern pool instead of referencing several different instances of String that have identical values.

It’s better to use:

 private static readonly object mutex = new object();

Also, since your string is not const or readonly, you can change it. So (in theory) it is possible to lock on your mutex. Change mutex to another reference, and then enter a critical section because the lock uses another object/reference. Example:

private static string mutex = "1";
private static string mutex2 = "1";  // for 'lock' mutex2 and mutex are the same

private static void CriticalButFlawedMethod() {
    lock(mutex) {
      mutex += "."; // Hey, now mutex points to another reference/object
      // You are free to re-enter
      ...
    }
}

More Related Contents:

  1. What are the differences between various threading synchronization options in C#?
  2. Concurrent HashSet in .NET Framework?
  3. Mutex example / tutorial? [closed]
  4. C# version of java’s synchronized keyword?
  5. How to protect resources that may be used in a multi-threaded or async environment?
  6. Monitor vs Mutex in c# [duplicate]
  7. Lock (Monitor) internal implementation in .NET
  8. SynchronizationLockException on Monitor.Exit when using await
  9. Synchronizing 2 processes using interprocess synchronizations objects – Mutex or AutoResetEvent
  10. WinForm Application UI Hangs during Long-Running Operation
  11. How can I wait for a thread to finish with .NET?
  12. Is it considered acceptable to not call Dispose() on a TPL Task object?
  13. Is using a Mutex to prevent multiple instances of the same program from running safe?
  14. Starting Tasks In foreach Loop Uses Value of Last Item [duplicate]
  15. Getting the thread ID from a thread
  16. Is EndInvoke() optional, sort-of optional, or definitely not optional?
  17. Thread safety of a Dictionary with multiple concurrent readers and no writers
  18. How to give priority to privileged thread in mutex locking?
  19. ThreadPool.QueueUserWorkItem vs Task.Factory.StartNew
  20. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  21. How do I implement the Sieve Of Eratosthenes using multithreaded C#?
  22. Why am I getting this error:”Cross-thread operation not valid: Control lbFolders accessed from a thread other than the thread it was created on.”?
  23. Can you link to a good example of using BackgroundWorker without placing it on a form as a component?
  24. How to use the CancellationToken without throwing/catching an exception?
  25. C# Threading/Async: Running a task in the background while UI is interactable
  26. How do you pass a BitmapImage from a background thread to the UI thread in WPF?
  27. Is Stopwatch.ElapsedTicks threadsafe?
  28. ReleaseSemaphore does not release the semaphore
  29. Calling an async method from a synchronous method
  30. Draw on a form by a separate thread

Leave a Comment