Did you call ShutdownProtobufLibrary() before exiting the process?

On Fri, Aug 28, 2009 at 12:05 PM, bgg <bru...@gmail.com> wrote:

>
> I'm using the C++ interface for protocol buffers.  In my code I don't
> declare any protocol buffers objects on the stack.  I have pointers to
> them declared.  I have built the protocol buffers library into
> libprotobuf.so.  In a code path that never calls any constructors I
> get dozens of valgrind errors like this (I replaced project paths
> with ... below):
>
> ==21149== 8 bytes in 1 blocks are still reachable in loss record 1 of
> 43
> ==21149==    at 0x4A06019: operator new(unsigned long)
> (vg_replace_malloc.c:167)
> ==21149==    by 0x50F2ED2:
> google::protobuf::internal::InitShutdownFunctions() (common.cc:307)
> ==21149==    by 0x3FFEA0BA32: pthread_once (in /lib64/
> libpthread-2.5.so)
> ==21149==    by 0x50F361C: google::protobuf::internal::OnShutdown(void
> (*)()) (once.h:114)
> ==21149==    by 0x3FFEA0BA32: pthread_once (in /lib64/
> libpthread-2.5.so)
> ==21149==    by 0x50F773A:
> google::protobuf::DescriptorPool::InternalAddGeneratedFile(void
> const*, int) (once.h:114)
> ==21149==    by 0x512FCAD:
> google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto
> () (descriptor.pb.cc:587)
> ==21149==    by 0x513050E: __static_initialization_and_destruction_0
> (int, int) (descriptor.pb.cc:632)
> ==21149==    by 0x516BA05: (within /home/bruceg/project/.../Linux-
> x86_64/lib/libprotobuf.so.4.0.0)
> ==21149==    by 0x50EE62A: (within /home/bruceg/project/.../Linux-
> x86_64/lib/libprotobuf.so.4.0.0)
> ==21149==
> ==21149==
>
> Does this look familiar to any one?
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to