Question

    private const int Total = 500000;
    private static volatile int _count = 0;

    private static void Main()
    {
        Task task = Task.Factory.StartNew(Decrement);
        for (int i = 0; i < Total; i++)
        {
            _count++;
        }

        task.Wait();
        Console.WriteLine(_count);

        Console.ReadLine();
    }

    private static void Decrement()
    {
        for (int i = 0; i < Total; i++)
        {
            _count--;
        }
    }

Sometimes the result is 0,sometimes the result is -xxxxxx. I don’t know why. Can anybody explain it and tell me the correct usage.

Answer 1

volatile guarantees no reordering of operations and disable caching optimizations, but does not guarantees thread safety – so you can get any result from 0 to -Total (if every pair of -- and ++ are properly mixed). I’ve covered “preper mixing” in answer to Why the following C# multi-threaded code does not output zero though it does in debugger?.

volatile is useful when you expect someone else to modify value so your code always reads reasonably recent value, which also will be consistent (i.e. for ++ you’ll not get int consisting of high part of 0xffff and low part of (0xffff+1) – you’ll get either one or another) since volatile is only applicable to types that are writen atomically.

If you want to modify counter in 2 threads – use Interlocked.Increment/Interlocked.Decrement.