Opened 9 years ago

Closed 9 years ago

#8244 closed defect (fixed)

Repeated TV: Attempting to change from None to None rapidly fills log

Reported by: Marc Randolph <mrand@…> Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - General Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Wife unit tried to switch to LiveTV to watch a show that started at 19:00. All she received was a blank screen. She left it there until I got home at 20:02. I'm sorry to say that I didn't have the presence of mind to do an strace or gdb before hitting escape.

I later found the frontend log to be filled with 29000 occurrences (eight a second) of:

Repeated TV: Attempting to change from None to None

  1. Any idea what caused a lockup that resulted in a change from None to None, and therefore a blank screen?
  1. Is there any way that the logging function, upon receiving the same message as the previous message, could wait at least a second, if not more, to log an identical message to prevent hyperactive messages like this one from filling up logs in record time?
$ mythfrontend --version
Please include all output in bug reports.
MythTV Version   : 23789
MythTV Branch    : branches/release-0-23-fixes
Network Protocol : 56
Library API      : 0.23.20100314-1
QT Version       : 4.5.2
Options compiled in:
 linux profile using_oss using_alsa using_pulse using_jack using_pulseoutput using_backend using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

Attachments (5)

mythfrontend.log.gz (85.8 KB) - added by Marc Randolph <mrand@…> 9 years ago.
Stacktrace.txt (5.5 KB) - added by Marc Randolph <mrand@…> 9 years ago.
Stack trace from different user with same repeated message in front-end log
ThreadStacktrace.txt (12.9 KB) - added by Marc Randolph <mrand@…> 9 years ago.
Threadtrace to go with stacktrace
mythfrontend.gdb.log (34.3 KB) - added by Marc Randolph <mrand@…> 9 years ago.
bt by attaching gdb to hung frontend
mythfrontend.strace.txt (33.1 KB) - added by Marc Randolph <mrand@…> 9 years ago.
strace of hung frontend

Download all attachments as: .zip

Change History (8)

Changed 9 years ago by Marc Randolph <mrand@…>

Attachment: mythfrontend.log.gz added

Changed 9 years ago by Marc Randolph <mrand@…>

Attachment: Stacktrace.txt added

Stack trace from different user with same repeated message in front-end log

Changed 9 years ago by Marc Randolph <mrand@…>

Attachment: ThreadStacktrace.txt added

Threadtrace to go with stacktrace

comment:1 Changed 9 years ago by Marc Randolph <mrand@…>

A user actually had his front-end crash (rather than hang like mine) when this occurred. Can't guarantee it is the same thing, but at first glance it appears to be, so attaching (even if they are much less than ideal traces - here's to hoping they help in some small way).

Changed 9 years ago by Marc Randolph <mrand@…>

Attachment: mythfrontend.gdb.log added

bt by attaching gdb to hung frontend

Changed 9 years ago by Marc Randolph <mrand@…>

Attachment: mythfrontend.strace.txt added

strace of hung frontend

comment:2 Changed 9 years ago by Marc Randolph <mrand@…>

Another occurrence

comment:3 Changed 9 years ago by robertm

Resolution: fixed
Status: newclosed

Should no longer be possible in trunk.

Note: See TracTickets for help on using tickets.