High memory usage by ModemManager

[Aleksander Morgado]

Hey!

>
> > ==5713== 7,180 bytes in 340 blocks are still reachable in loss record 1,180 of 1,184
> > ==5713==    at 0x4847DC8: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> > ==5713==
> > ==5713== 42,766 bytes in 232 blocks are still reachable in loss record 1,181 of 1,184
> > ==5713==    at 0x484AB84: realloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> > ==5713==
> > ==5713== 81,777 bytes in 2,312 blocks are still reachable in loss record 1,182 of 1,184
> > ==5713==    at 0x4847EB4: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> > ==5713==
> > ==5713== 101,244 bytes in 1,709 blocks are still reachable in loss record 1,183 of 1,184
> > ==5713==    at 0x484A904: calloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> > ==5713==
> > ==5713== 128,358 (128,324 direct, 34 indirect) bytes in 4,583 blocks are definitely lost in loss record 1,184 of 1,184
> > ==5713==    at 0x4847EB4: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
> > ==5713==
>
> This one above is the leak we should take care of. I'll try to play
> with enabling GPS and let's see what I get in my valgrind tests.
>

I believe I have the fix already, please see
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/243/commits

-- 
Aleksander
https://aleksander.es