Ok guys thanks for all the responses. Having studied this a bit more
closely I can recap that protobuf messages are what's called
effectively immutable (according to terminology used in Brian
Goetz's book p.52-53) and need to be safely published to be used
across multiple threads. Just like Evan
I have found a segfault when using the CPP implementation from python
in 2.4.1. I can reproduce it in two different environments with a
small number of files.
The segfault is happening in google/protobuf/internal/cpp_message.py
in the ScalarProperty getter. There seems to be some interplay
