std::map thread-safety

Question

Is reference to object in std::map is thread safe?

std::map< std::string, Object >   _objects;

Answer 1

The C++11 standard guarantees that const method access to containers is safe from different threads (ie, both use const methods).

In addition, [container.requirements.dataraces] states

implementations are required to avoid data races when the contents of the contained object in different elements in the same sequence, excepting vector<bool>

In other words, except for vector<bool> modifying distinct contents is not a data race.

Now, if one thread invalidates an iterator used by another thread, clearly this is a data race (and results in undefined behavior). If one thread does non- const access to a container, and another does const access, that is a data race (and undefined behavior). (Note: a number of functions are "considered const " for the purpose of multithreading, including begin , end and other functions (and methods) that are non- const simply because they return non- const iterators. [] is included in this set of pseudo- const for thread safety reasons, except for map and unordered_set etc -- 23.2.2.1).

However, it appears that if you have a reference to an element within the container, and engage in operations that do not invalidate that reference in another thread, and never write to that element in another thread, you can safely read from that reference. Similarly, if other threads never even read from the element, then writing to that element shouldn't result in undefined behavior.

For standards references, 17.6.5.9.5 seems to guarantee that functions from the standard library won't run away and read/write elements needlessly.

So the short answer: you are safe, so long as the other thread doesn't directly mess with that particular entry in the map .

Answer 2

Elements in a map are stable, they do not get moved or invalidated unless the element is erased from the map. If only one thread is writing to a given object, and changes to the map itself are correctly synchronized, then I believe it will be safe. I'm sure it's safe in practice, and I think it's safe in theory too.

The standard guarantees that distinct elements can be modified by different threads, in [container.requirements.dataraces]

Notwithstanding (17.6.5.9), implementations are required to avoid data races when the contents of the contained object in different elements in the same sequence, excepting vector<bool> , are modified concurrently.

This only allows you to modify the elements, not to insert new elements into the map while modifying elements. For some containers, such as std::vector , modifying the vector itself might also modify elements by reallocating and moving them, but [associative.reqmts]/9 ensures std::map won't invalidate existing elements.

Since no member function of std::map is required to access the second member of its elements (ie the mapped_type ) I think [res.on.data.races]/5 says no other thread will conflict with writes to that member when modifying the map. (Thanks to Yakk for that final piece of the puzzle)

Answer 3

The general gist from this thread (pun intended) is that adding or deleting elements to the map is not thread-safe but writing to the elements of a map is thread-safe. This however contradicts with what is concluded in other threads as they conclude that maps should be considered not<\/strong> thread-safe: https:\/\/codereview.stackexchange.com\/questions\/8715\/thread-safe-stdmap-accessor<\/a> and https:\/\/stackoverflow.com\/a\/9147296\/1688206<\/a>

"