“A reference to a volatile field will not be treated as volatile” implications

by

You are not doing anything wrong. According to the documentation:

A volatile field should not normally
be passed using a ref or out
parameter, since it will not be
treated as volatile within the scope
of the function. There are exceptions
to this, such as when calling an
interlocked API.

More Related Contents:

  1. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  2. Task vs Thread differences [duplicate]
  3. Maximum number of threads in a .NET app?
  4. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
  5. Multi-threaded splash screen in C#?
  6. Is it considered acceptable to not call Dispose() on a TPL Task object?
  7. Re-entrant locks in C#
  8. Getting the thread ID from a thread
  9. Multiple Parallel.ForEach loops in .Net
  10. What does SynchronizationContext do?
  11. Is there a way to indefinitely pause a thread?
  12. How to put a task to sleep (or delay) in C# 4.0?
  13. Task continuation on UI thread
  14. Is it OK to use a string as a lock object?
  15. Async/Await vs Threads
  16. Monitor vs lock
  17. Unhandled exceptions in BackgroundWorker
  18. Proper way to Dispose of a BackGroundWorker
  19. EF Data Context – Async/Await & Multithreading
  20. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  21. 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.”?
  22. Looking for an example of a custom SynchronizationContext (Required for unit testing)
  23. Can you link to a good example of using BackgroundWorker without placing it on a form as a component?
  24. How do I spawn threads on different CPU cores?
  25. Should thread-safe class have a memory barrier at the end of its constructor?
  26. Parallel doesnt work with Entity Framework
  27. Starting a new thread in a foreach loop
  28. Multithreaded NamePipeServer in C#
  29. Wrapping ManualResetEvent as awaitable task
  30. Half – fences and full fences? [duplicate]

Leave a Comment