[mythtv-users] Are there Memory leaks in 0.28 Mythfrontend?

[Greg Oliver]

On Mon, Apr 17, 2017 at 6:14 PM, Anthony Giggins <seven at seven.dorksville.net
> wrote:

> I'm seeing more and more that memory is creeping up on the frontend
> process, is this a known issue?
>
> I'm seeing this on 3 different frontends, the first one is a combined
> front end
>
>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
>  4766 seven     20   0 7347912 1.440g  77840 S   1.3 14.8 453:09.80
> mythfrontend.re
>
> $ mythfrontend --version
> xprop:  unable to open display ''
> Please attach all output as a file in bug reports.
> MythTV Version : v0.28.1-19-g0037461
> MythTV Branch : fixes/0.28
> Network Protocol : 88
> Library API : 0.28.20161120-1
> QT Version : 5.2.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl using_bindings_python
> using_bindings_php using_crystalhd using_dvb using_firewire using_frontend
> using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv
> using_joystick_menu using_libcec using_libcrypto using_libdns_sd
> using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl
> using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript
> using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr
> using_xv using_profiletype using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2
>
>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
>  5163 seven     20   0 8116840 2.396g  77392 S   2.6 62.1 851:26.40
> mythfrontend.re
>
> $ mythfrontend --version
> xprop:  unable to open display ''
> Please attach all output as a file in bug reports.
> MythTV Version : v0.28.1-18-g7026623
> MythTV Branch : fixes/0.28
> Network Protocol : 88
> Library API : 0.28.20161120-1
> QT Version : 5.5.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl using_bindings_python
> using_bindings_php using_crystalhd using_dvb using_firewire using_frontend
> using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv
> using_joystick_menu using_libcec using_libcrypto using_libdns_sd
> using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl
> using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript
> using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr
> using_xv using_profiletype using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2
>
>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
> 13671 seven     20   0 5507908 962424 105772 S   0.7 47.0 389:35.67
> mythfrontend.re
>
> $ mythfrontend --version
> xprop:  unable to open display ''
> Please attach all output as a file in bug reports.
> MythTV Version : v0.28.1-8-ge9be5e0
> MythTV Branch : fixes/0.28
> Network Protocol : 88
> Library API : 0.28.20161120-1
> QT Version : 5.5.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl using_bindings_python
> using_bindings_php using_crystalhd using_dvb using_firewire using_frontend
> using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv
> using_joystick_menu using_libcec using_libcrypto using_libdns_sd
> using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl
> using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript
> using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr
> using_xv using_profiletype using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2
>
> what troubleshooting do I need to provide to raise a bug? from previous
> threads I think this required valgrind? but can someone confirm?
>
> Cheers,
>
> Anthony
>
>
I posted a message Saturday with the same issues, but I guess it was over
the max size and the moderator did not approve it.  I have the same issue
since I upgraded to:

MythTV Version : v28.0-104-g3930f5d
MythTV Branch : fixes/0.28
Network Protocol : 88
Library API : 0.28.20161120-1
QT Version : 5.7.1

10 days in, my machine OOM'ed mythfronend - it was hogging 10GB ram when it
happened.  The previous 0.28 version (I do not have the specifics of
version) did not have this issue.  It ran for over a month with no issues -
well, at least it did not OOM.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170418/36533d64/attachment.html>