Opened 12 years ago
Closed 11 years ago
#11105 closed Bug Report - Crash (Duplicate)
Mythnetvision crashes frontend (YouTube)
Reported by: | Owned by: | Jonatan Lindblad | |
---|---|---|---|
Priority: | minor | Milestone: | 0.26.1 |
Component: | Plugin - MythNetvision | Version: | Unspecified |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Thread on users list with info: http://www.gossamer-threads.com/lists/mythtv/users/527697
Basically, when I view a YouTube? video using Mythnetvision, it crashes the frontend. Seems to be the same when I exit mid video or let it play to the end.
Have tried with different themes and still see the same issue.
Happens virtually every time, but not consistently
Log file (mythfrontend -v all)
Backtrace:
Running Ubuntu 12.04 x86, with Mythtv from Mythbuntu builds
mythbackend --version Please attach all output as a file in bug reports. MythTV Version : v0.25.2-19-gcf06841 MythTV Branch : fixes/0.25 Network Protocol : 72 Library API : 0.25.20120506-1 QT Version : 4.8.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_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
Change History (4)
comment:1 Changed 11 years ago by
Status: | new → infoneeded_new |
---|
comment:2 Changed 11 years ago by
Owner: | set to Jonatan Lindblad |
---|
The backtrace doesn't show where the crash is happening so it isn't helping very much.
I can take another look if you can provide a backtrace that doesn't end with something like this:
You should also upgrade to latest fixes/0.25 or fixes/0.26 where #11168 was fixed.