Develop those things: how to solve the memory leak in the conversion between go and C type?

Last time I shared with you about Go Add C.free Free memory , Solution to error reporting in compilation , Let's discuss with you today Go And C How to solve the memory leak in type conversion .

We found in the development process that , take Go character string 、byte Slice to C The corresponding string 、 Array time , If memory is not freed , Memory leakage will occur .

The solution is as follows ：

When Go character string 、byte Slice to C The corresponding string 、 Array time , Due to the use malloc Allocate space , So you need to use C.free Free memory , Avoid memory leaks .

Verification process ：

Just call C.CString Do not call C.free Free memory , After a few seconds , The memory rises to more than 20 M, And has been rising ：

When calling the C.free After releasing memory , The memory of the program has been stable 7M about , Pictured ：

stay CGO In the official document , stay CString And CBytes The Department also specifically pointed out , You need to free memory after using . Especially in video surveillance with high concurrency 、 In high-performance scenarios , We need to call relevant methods in time to release resources in time , Avoid temporary or permanent memory leaks , Thus affecting the normal use of the platform .

 TSINGSEE Qingxi video focuses on the research and development of video streaming media technology , At present, diversified video platforms have been launched for the market , Such as EasyCVR、EasyGBS、EasyDSS、EasyNVR etc. , It can realize the access of multiple types of equipment 、 Multi protocol support 、 Multi format video stream output 、 Multi terminal platform compatibility , The platform can be applied to smart construction sites 、 Smart campus 、 Smart factory 、 Intelligent water conservancy 、 In scenarios such as smart communities . Interested users can go to the demonstration platform for experience or deployment testing .