xmingc
Do you locate the leak?
I also encountered `segment fault` in online mode. But that is too rare to locate the leak. Hope we can find it out together.
Don't worry about programming. Should you get any traces trigger that, you can send me for further check. : )
Yeah I think you get the point. I will walk through and check the memory free tomorrow.
http message leak fixed (f71d4ffe33a5be889fd4757c10edae67e6d1fcf1) and check other malloc and free over. If other errors found, let me know. Thanks you : )
Sry for late response. I was away for my vacation last days. I will check your findings and make it correct. Thanks!
The valgrind report link is outdated. Could you give me a new one? I think I can locate the problem quickly with some clear clue.
> Thank you for reporting this. We will fix it soon. > > If you want a quick fix with your own build, change > > https://github.com/kubernetes-client/c/blob/9a78e0fe02dac4aa65b86d98a7fa894be2fee872/kubernetes/model/v1_object_meta.c#L354 > > to...
@ityuhui as I tested, mere upgrading cJSON does NOT fix this problem. Latest cJSON just enhanced `current_element` validity check in `get_object_item`, not fixed our problem.
Thanks!