Open manthanrtilva opened 1 year ago
Here is PR to resolve this memory leak. https://github.com/eclipse/mosquitto/pull/2787
Thank you for the report, and for the PR. I am in two minds about this. On one hand, I prefer to be completely valgrind clean. On the other hand, this is a tiny leak that happens when the broker is exiting anyway, so it doesn't really matter. The related code is completely refactored in the develop branch and so this issue will not be present in 2.1.
Merging the PR may well produce conflicts when merging back into the develop branch, which I'd really prefer to avoid.
On balance, I'd like to leave this as it is. Saving a single 330 byte leak per plugin and that happens only on exit, doesn't feel like a good reason to make life more difficult. What do you think?
@ralight Sound good to leave it, if it will be getting resolved in next version.
OS info
mosquitto info
How to reproduce memory leak.