Perhaps you could use protobuf-c which uses global variables for its metadata and hence has no leaks upon unload (as long as you free all your messages of course).
- dave On Mar 4, 4:08 am, Ivan Kharin <korsar.ak...@gmail.com> wrote: > > I'm using protocol buffers in my project (C++), and while I was > > hunting for memory leaks, I discovered that in the generated code, > > static members are being allocated, but there's no way to free them. > > yes. > > > It's not a major issue, because the leak only occur when you exit the > > application (and the static members are not being free as they > > should), but I would like to know if you are aware of this issue, and > > is there a workaround or any other solution? > > it's major issue if PB used in shared library with load/call/unload usage > pattern :( > > -- > Ivan Kharin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
