C# multi-threading: Acquire read lock necessary?

by

The short answer is: it depends.

The long answer is:

  • If it is not a shared value, i.e, only one thread can see it (or use it), you don’t need any synchronization.

  • If it is an immutable value, i.e., you set it only once and then only ever read, it is safe to do so without synchronization (as long as you don’t start reading before the first write completes).

  • If it is a “primitive” type of at most 32-bits (e.g. byte, short, int) you can get stale (old) data when reading. If that doesn’t bother you, you’re set. If stale data is undesirable, making the variable volatile can fix this problem without additional synchronization for reads. But if you have racing writers, you will need to follow the same advice as for longs below.

  • If it is a “primitive” type longer than 32-bits (e.g. long, decimal, double) you need synchronization, otherwise you could read “half” of one value, “half” of another, and get crazy results. For this the recommended approach is to use the methods in the Interlocked class, for both reads and writes..

  • If it is a reference type, you will need synchronization to avoid seeing an invalid state (Jeff Lamb’s picture example is a good one). The lock statement might be enough for that. Again, you need to lock for both reads and writes.

There are some other points to consider (how long to lock, for example), but I think these are enough to answer your question.

More Related Contents:

  1. What’s wrong with using Thread.Abort()
  2. Use Unity API from another Thread or call a function in the main Thread
  3. Volatile vs. Interlocked vs. lock
  4. When should the volatile keyword be used in C#?
  5. Is there a way of setting culture for a whole application? All current threads and new threads?
  6. Change WPF controls from a non-main thread using Dispatcher.Invoke
  7. Killing a .NET thread
  8. How to kill a thread instantly in C#?
  9. Alternatives to Thread.Sleep()
  10. Updating an ObservableCollection in a separate thread
  11. Why do I need a memory barrier?
  12. Unable to use more than one processor group for my threads in a C# app
  13. Why does this simple .NET console app have so many threads?
  14. SpinWait vs Sleep waiting. Which one to use?
  15. Task.Yield – real usages?
  16. How to catch exceptions from a ThreadPool.QueueUserWorkItem?
  17. What thread runs the code after the `await` keyword?
  18. WPF UI multitasking
  19. C# manual lock/unlock
  20. How to make make a .NET COM object apartment-threaded?
  21. Show Loading animation during loading data in other thread
  22. Is this use of Parallel.ForEach() thread safe?
  23. WaitAll for multiple handles on a STA thread is not supported
  24. “Context cannot be used while the model is being created” exception with ASP.NET Identity
  25. Thread Safe Properties in C#
  26. The lack of non-capturing Task.Yield forces me to use Task.Run, why follow that?
  27. How to create a thread?
  28. How to pause/suspend a thread then continue it?
  29. Restarting a thread in .NET (using C#)
  30. Multithreaded NamePipeServer in C#

Leave a Comment