Use MessageLite instead when you only need the subset of features which it supports – namely, nothing that uses descriptors or reflection. Non-lite messages additionally implement the Message interface, which is a subclass of MessageLite. This interface is implemented by all protocol message objects. Interface to light weight protocol messages. Furthermore this call is not thread safe, user needs to synchronize multiple calls. However, it is not safe to use any other part of the protocol buffers library after ShutdownProtobufLibrary() has been called. You are writing a dynamically-loaded library which needs to clean up after itself when the library is unloaded.You use a draconian definition of "memory leak" in which you expect every single malloc() to have a corresponding free(), even for objects which live until program exit.There are two reasons you might want to call this: ![]() ![]() Shut down the entire protocol buffers library, deleting all static-duration objects allocated by the library or by generated.
0 Comments
Leave a Reply. |