We have a protobuf message defined in the following way:
message ModuleEntry
{
optional uint32 id = 1;
optional string name = 2;
optional uint32 type = 3;
repeated ParameterEntry parameter = 4;
repeated ModuleEntry subModules = 5;
optional uint32 usage = 6;
optional
On Thu, Jan 30, 2014 at 6:48 AM, Øyvind Bakken oyv...@gmail.com wrote:
We have a protobuf message defined in the following way:
message ModuleEntry
{
optional uint32 id = 1;
optional string name = 2;
optional uint32 type = 3;
repeated ParameterEntry parameter = 4;
std::bad_alloc comes from your system's memory allocator, not from protocol
buffers. I would guess that the round number is because it creates buckets
for each allocation size, and you aren't allocating anything else that is
the same size as B. So 0x100 is your system's bucket limit.
You
Hi there, I have a simple message defined with a repeated field. The
repeated field type is another message type. For example:
Message A {
repeated B b = 1;
}
Message B {
required uint32 x = 1;
}
I'm building up a single A message in memory with quite a few B's. I
am constantly receveiving
