[mythtv-commits] Ticket #9707: Memory leak during playback of recent recordings (PVR-250)

MythTV noreply at mythtv.org
Sun Apr 17 16:34:25 UTC 2011


#9707: Memory leak during playback of recent recordings (PVR-250)
-----------------------------------------+--------------------------------
 Reporter:  aaron <memoryguy@…>          |          Owner:  janne
     Type:  Bug Report - General         |         Status:  infoneeded_new
 Priority:  minor                        |      Milestone:  unknown
Component:  MythTV - Video Playback      |        Version:  Unspecified
 Severity:  medium                       |     Resolution:
 Keywords:                               |  Ticket locked:  0
-----------------------------------------+--------------------------------

Comment (by aaron <memoryguy@…>):

 I updated to version:


 {{{
 myth at myth:~$ mythbackend --version
 Please attach all output as a file in bug reports.
 MythTV Version   : v0.25pre-1788-g0e22930
 MythTV Branch    : master
 Network Protocol : 65
 Library API      : 0.25.20110414-3
 QT Version       : 4.5.1
 Options compiled in:
  linux profile 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

 }}}

 And ran valgrind again. I think it might have worked better this time...
 the video was actually getting (slowly) updated --- one frame every few
 seconds --- and the VIRT was increasing. It went from around 960 MB at the
 start of playback to 1021 MB at the time I stopped. It took about half an
 hour to get that far, although based on the video frames, only a couple of
 minutes (if even that much) had played. Hopefully it shows something
 useful. The log is too large to attach so I put it in my Dropbox:

 [http://dl.dropbox.com/u/1897138/valgrind_logs_1788.tar.gz]

 This time the log seems to be complete, and I don't think it says anything
 about memory corruption. Please let me know if there is anything more you
 want me to collect.

 Thanks!
 aaron

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/9707#comment:4>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list