Opened 18 years ago
Closed 18 years ago
#5436 closed defect (invalid)
Mythbackend leaks memory
| Reported by: | udo | Owned by: | Isaac Richards |
|---|---|---|---|
| Priority: | major | Milestone: | unknown |
| Component: | mythtv | Version: | 0.21-fixes |
| Severity: | medium | Keywords: | |
| Cc: | udovdh@… | Ticket locked: | yes |
Description
The memory usage of mythbackend increases over time (days, weeks). This could point point to one or more memory leaks.
[root@recorder redhat]# mythfrontend --version Please include all output in bug reports. MythTV Version : exported MythTV Branch : branches/release-0-21-fixes Library API : 0.21.20080304-1 Network Protocol : 40 Options compiled in:
linux release using_oss using_alsa using_backend using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun using_iptv using_ivtv using_joystick_menu using_lirc using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw using_xvmc_vld using_bindings_perl using_bindings_python using_opengl using_ffmpeg_threads using_libavc_5_3 using_live
upnp is disabled; this has no effect on memory consumption memory geos from a few % to 40% over time.
Change History (3)
comment:1 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 18 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → new |
Excuse me? 1GB box, starts with few % memory usage. Ends up with 40+% memory for mythbackend. Enough evidence for me. Or can you convince me otherwise?
comment:3 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
| Ticket locked: | set |

No valgrind log, not even evidence of increased memory usage?