Ebulus7899

I also finding issues with this. Project needs to update mongoose to fix a bug however I now find this package never no longer functions properly.

Thankss for the reply. I tried updating to the latest version of libyang 2.1 (2.1.148) to see if that changed any behaviour. The following stack traces are for that version....

As an added bit of information I have possibly found the leak. The allocation is happening here ```c out->method.mem.buf = ly_realloc(*out->method.mem.buf, new_mem_size); if (!*out->method.mem.buf) { out->method.mem.len = 0; out->method.mem.size =...

Changing the 0 to a 1 and I get =85529== LEAK SUMMARY: ==85529== definitely lost: 0 bytes in 0 blocks ==85529== indirectly lost: 0 bytes in 0 blocks ==85529== possibly...

Sorry my mistake. Thank you for the reply. It seems that the actual culprit would be the yang3 package making use of the libyang library. ``` fn print_string( &self, format:...