#898 Memory leaks

Current_GIT
invalid
nobody
Mumble (544)
unspecified
5
2013-12-16
2012-07-30
Anonymous
No

Seems like mumble is leaking memory. Memory usage was up to 1.4GiB of RAM and was slowly increesing.
Compiled mumble with traces and then ran valgrind with this command valgrind --tool=memcheck --leak-check=full mumble

Arch Linux
3.4.6-1-ARCH
Pulseaudio 2.1-1
Asus Xonar Essence STX

Results; (whole report attached)
http://pastebin.se/hPIff81X

==6180== LEAK SUMMARY:
==6180== definitely lost: 11,888 bytes in 34 blocks
==6180== indirectly lost: 43,296 bytes in 1,345 blocks
==6180== possibly lost: 1,195,176 bytes in 15,885 blocks
==6180== still reachable: 12,143,546 bytes in 71,806 blocks
==6180== suppressed: 0 bytes in 0 blocks
==6180== Reachable blocks (those to which a pointer was found) are not shown.
==6180== To see them, rerun with: --leak-check=full --show-reachable=yes
==6180==
==6180== For counts of detected and suppressed errors, rerun with: -v
==6180== Use --track-origins=yes to see where uninitialised values come from
==6180== ERROR SUMMARY: 3942056 errors from 2063 contexts (suppressed: 53 from 10)

Discussion

  • Kissaki
    Kissaki
    2012-10-19

    Thank you for reporting, but the logs are not available any more.
    Could you rehost them?

     
  • Stefan H.
    Stefan H.
    2012-11-05

    Can't reproduce

     
  • Stefan H.
    Stefan H.
    2012-11-05

    • status: open --> pending
     
  • jaybocc2
    jaybocc2
    2013-04-13

    i just ran into a huge memory leak on debian wheezy with mumble:

     
  • Kissaki
    Kissaki
    2013-12-16

    • status: pending --> invalid
    • Version: --> unspecified
     
  • Kissaki
    Kissaki
    2013-12-16

    Can not do anything with this.