Hi Loic, On Wed, Dec 7, 2016 at 3:44 PM, Loic Poulain <loic.poulain@xxxxxxxxx> wrote: > Valgrind reports "timeout_data" as definitely lost. > Fix this issue in timeout_destroy function. > --- > src/shared/mainloop.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/src/shared/mainloop.c b/src/shared/mainloop.c > index eacb6a4..09c46a7 100644 > --- a/src/shared/mainloop.c > +++ b/src/shared/mainloop.c > @@ -283,6 +283,8 @@ static void timeout_destroy(void *user_data) > > if (data->destroy) > data->destroy(data->user_data); > + > + free(data); > } Seems valid but can you add the backtrace, I wonder how we didn't spot this before so perhaps the backtrace would explain it. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html