Are IEnumerable Linq methods thread-safe?

by

The interface IEnumerable<T> is not thread safe. See the documentation on http://msdn.microsoft.com/en-us/library/s793z9y2.aspx, which states:

An enumerator remains valid as long as the collection remains unchanged. If changes are made to the collection, such as adding, modifying, or deleting elements, the enumerator is irrecoverably invalidated and its behavior is undefined.

The enumerator does not have exclusive access to the collection; therefore, enumerating through a collection is intrinsically not a thread-safe procedure. To guarantee thread safety during enumeration, you can lock the collection during the entire enumeration. To allow the collection to be accessed by multiple threads for reading and writing, you must implement your own synchronization.

Linq does not change any of this.

Locking can obviously be used to synchronize access to objects. You must lock the object everywhere you access it though, not just when iterating over it.

Declaring the collection as volatile will have no positive effect. It only results in a memory barrier before a read and after a write of the reference to the collection. It does not synchronize collection reading or writing.

More Related Contents:

  1. Create Dynamic Threads in c# [closed]
  2. Automating the InvokeRequired code pattern
  3. What operations are atomic in C#?
  4. Concurrent HashSet in .NET Framework?
  5. Are C# arrays thread safe?
  6. reference assignment is atomic so why is Interlocked.Exchange(ref Object, Object) needed?
  7. How to create a task (TPL) running a STA thread?
  8. Why we need Thread.MemoryBarrier()?
  9. Why do I need a memory barrier?
  10. Thread safety of a Dictionary with multiple concurrent readers and no writers
  11. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  12. thread with multiple parameters
  13. Event handlers not thread safe? [duplicate]
  14. Is this use of Parallel.ForEach() thread safe?
  15. How to correctly read an Interlocked.Increment’ed int field?
  16. Thread Safe Properties in C#
  17. Is it safe to use a boolean flag to stop a thread from running in C#
  18. ConcurrentDictionary Pitfall – Are delegates factories from GetOrAdd and AddOrUpdate synchronized?
  19. Thread safety on readonly static field initialisation
  20. Is Stopwatch.ElapsedTicks threadsafe?
  21. C# Thread safe fast(est) counter
  22. C# and thread-safety of a bool
  23. Is it possible to observe a partially-constructed object from another thread?
  24. SqlConnection Thread-Safe?
  25. Writing to file in a thread safe manner
  26. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  27. Is it OK to use a string as a lock object?
  28. Why CancellationToken is separate from CancellationTokenSource?
  29. Async WebApi Thread.CurrentCulture
  30. Multithreaded NamePipeServer in C#

Leave a Comment