[mythtv-commits] Ticket #9707: Memory leak during playback of recent recordings (PVR-250)
MythTV
noreply at mythtv.org
Sat Apr 2 15:35:17 UTC 2011
#9707: Memory leak during playback of recent recordings (PVR-250)
-----------------------------------------+-----------------------------
Reporter: aaron <memoryguy@…> | Owner: janne
Type: Bug Report - General | Status: new
Priority: minor | Milestone: unknown
Component: MythTV - Video Playback | Version: Unspecified
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-----------------------------------------+-----------------------------
Description changed by wagnerrp:
Old description:
> Recordings made in the last month or so seem to make mythfrontend leak
> memory during playback. Typically I use timestretch 1.3x or higher, up to
> 2x, not sure if it is relevant. About halfway through a one hour program
> I have to restart the frontend to release the memory; playback gets
> stuttery due to excessive paging.
>
> All of my recordings are standard-def MPEG2, produced from a PVR-250. But
> only the more recent recordings show this problem.
>
> My backend/frontend has 512 MB of RAM (+2 GB paging space). When the
> frontend needs to be restarted, htop reports the "VIRT" at 800+ MB.
>
> After starting the frontend VIRT is 337 MB.
>
> I am running master built from git. The current version I am running (and
> do see the problem) is:
>
>
> {{{
> $ mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v0.25pre-1625-gbbf345c
> MythTV Branch : master
> Network Protocol : 65
> Library API : 0.25.20110328-2
> QT Version : 4.5.1
> Options compiled in:
> linux release use_hidesyms using_alsa using_oss using_backend
> using_bindings_perl using_bindings_python using_bindings_php using_dvb
> using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv
> using_libxml2 using_libudf using_lirc using_mheg using_qtdbus
> using_qtwebkit using_v4l using_x11 using_xrandr using_xv
> using_bindings_perl using_bindings_python using_bindings_php
> using_mythtranscode using_opengl using_ffmpeg_threads using_live
> using_mheg using_libxml2 using_libudf
> }}}
>
> I have tried to run valgrind:
>
> {{{
> valgrind --log-file=vglog.log --leak-check=full --error-limit=no --show-
> reachable=yes mythfrontend -O UIPainter=qt
> }}}
>
> When I started playback it complained about not being able to
> allocate/resize ALSA buffers, and it looked like it was not using the
> proper playback timing methods. Perhaps this is because I was using an
> SSH session (although displaying on the local display, not remote).
> Hopefully the log managed to capture something meaningful.
>
> Playback stuttered horribly with valgrind running, so I left it going as
> long as I could stand.
>
> Attached are the frontend output and valgrind log.
>
> Please let me know if there is something else that would be helpful.
New description:
Recordings made in the last month or so seem to make mythfrontend leak
memory during playback. Typically I use timestretch 1.3x or higher, up to
2x, not sure if it is relevant. About halfway through a one hour program I
have to restart the frontend to release the memory; playback gets stuttery
due to excessive paging.
All of my recordings are standard-def MPEG2, produced from a PVR-250. But
only the more recent recordings show this problem.
My backend/frontend has 512 MB of RAM (+2 GB paging space). When the
frontend needs to be restarted, htop reports the "VIRT" at 800+ MB.
After starting the frontend VIRT is 337 MB.
I am running master built from git. The current version I am running (and
do see the problem) is:
I have tried to run valgrind:
{{{
valgrind --log-file=vglog.log --leak-check=full --error-limit=no --show-
reachable=yes mythfrontend -O UIPainter=qt
}}}
When I started playback it complained about not being able to
allocate/resize ALSA buffers, and it looked like it was not using the
proper playback timing methods. Perhaps this is because I was using an SSH
session (although displaying on the local display, not remote). Hopefully
the log managed to capture something meaningful.
Playback stuttered horribly with valgrind running, so I left it going as
long as I could stand.
Attached are the frontend output and valgrind log.
Please let me know if there is something else that would be helpful.
--
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9707#comment:1>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list