Opened 13 years ago

Closed 12 years ago

#4933 closed defect (fixed)

memory leak when upnp is enabled in mythbackend

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no


we've seen reports by some Ubuntu users whose backends would consume lots of memory after running for a few hours. When mythbackend is ran with--noupnp, memory usage stays low. It doesn't matter whether those users have upnp enabled devices on their network or not. For one user (who has some upnp devices), mythbackend will also consume 100% CPU time.

Nico provided some valgrind logs gathered with

valgrind --leak-check=full --error-limit=no --show-reachable=yes --log-
file=logfile -v -- /usr/bin/mythbackend --daemon --logfile
/var/log/mythtv/mythbackend.log --pidfile
/var/run/mythtv/ | tee backend.log

Attachments (1)

logfile.21733.gz (52.8 KB) - added by camelreef 13 years ago.
valgrind log, gzipped

Download all attachments as: .zip

Change History (4)

comment:1 Changed 13 years ago by laga@…

I can't attach the valgrind log because it is too big. You can get it from Launchpad: The Ubuntu bug report can be found at

This problem happens with 0.21.

Changed 13 years ago by camelreef

Attachment: logfile.21733.gz added

valgrind log, gzipped

comment:2 Changed 13 years ago by camelreef

Here is the log, text compresses fine.


comment:3 Changed 12 years ago by Dibblah

Resolution: fixed
Status: newclosed

Should be fixed in trunk as part of [18011]

Note: See TracTickets for help on using tickets.