keepsimple1

Thanks for the details! > Test1 v0.13.6 (without extra logging, just tracking memory externally) Is the "Memory Usage over Time" showing the total memory used by the program that uses...

I will try to do something similar locally and see if I can find anything.

I tried to run a program similar to your code in (https://github.com/keepsimple1/mdns-sd/issues/337#issuecomment-2794240225) , but could not reproduce the issue yet. But I wanted to try something related to `stop_browse`: opened...

Thanks for testing! This is awesome! I've merged the changes and published a new release 0.13.7. If any problems, please let me know.

@clarkholdham just wanted to circle back, is there anything else not addressed for this issue? If not, I will close this issue soon. Thanks!

Thanks for getting back and the details! > This may warant another ticket if you wish to investigate further seperately. Yes I think that's a good idea. Please open a...

I tried out valgrind with your test program. I saw similar output. Looks like valgrind reports `possibly lost` because the daemon thread did not get chance to free the memory...

Closing now as the original memory issue is fixed. The most recent valgrind mem report seems to be false positives based on my testing (detailed see the above). If not,...

Interesting and a valid point. I'm not actively using IPv6 so didn't realize that. > Would it be possible to include the scope/interface information in the resolved record? I think...

> I can look into it and start implementing it, it's not that urgent, I'll create a Pull Request when ready. Thanks for willing to look into it! Of course....