Opened 9 years ago

Closed 9 years ago

#8642 closed defect (invalid)

Multiple mythbackends in CPU Queue that never exit

Reported by: Ken Emerson <kenneth.emerson@…> Owned by: stuartm
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I have noticed recently that there are many instances of mythbackend in the CPU queue and the number continues to climb over time. I attached to a couple of the processes and they seem to be stuck at the same place. Traceback below as well as snapshot of CPUQ.

Please attach all output as a file in bug reports. MythTV Version : 25260 MythTV Branch : trunk Network Protocol : 57 Library API : 0.23.20100701-1 QT Version : 4.5.2 Options compiled in:

linux debug using_oss using_alsa using_backend using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 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_live using_mheg

F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD

0 S 1001 2055 2054 0 89 9 - 26125 futex_ ? 00:00:00 mythbackend

0 S 1001 2102 2101 0 89 9 - 26117 futex_ ? 00:00:00 mythbackend

0 S 1001 2117 2116 0 89 9 - 26117 futex_ ? 00:00:00 mythbackend

0 S 1001 6720 6719 0 89 9 - 26117 futex_ ? 00:00:00 mythbackend

0 S 1001 9541 9516 7 80 0 - 139591 poll_s ? 00:33:32 mythfrontend

1 Z 1001 9775 9541 0 80 0 - 0 exit ? 00:00:00 mythfrontend <defunct>

1 Z 1001 9776 9541 0 80 0 - 0 exit ? 00:00:00 mythfrontend <defunct>

1 Z 1001 9778 9541 0 80 0 - 0 exit ? 00:00:00 mythfrontend <defunct>

1 Z 1001 9779 9541 0 80 0 - 0 exit ? 00:00:00 mythfrontend <defunct>

1 S 1001 23651 1 0 80 0 - 95035 poll_s ? 00:02:32 mythbackend

0 S 1001 29079 29078 0 89 9 - 26117 futex_ ? 00:00:00 mythbackend

0 S 1001 32275 32268 0 89 9 - 26117 futex_ ? 00:00:00 mythbackend

#0 0x00e83422 in kernel_vsyscall () #1 0x02896e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x047ebe67 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0x047eaec9 in QThread::wait(unsigned long) () from /usr/lib/libQtCore.so.4 #4 0x058576ee in ~WorkerThread? (this=0x8b76ea0, in_chrg=<value optimized out>) at threadpool.cpp:180 #5 0x0585d020 in ~HttpWorkerThread? (this=0x8b76ea0, in_chrg=<value optimized out>) at httpserver.cpp:219 #6 0x05858999 in ~ThreadPool? (this=0x8b75378, in_chrg=<value optimized out>) at threadpool.cpp:328 #7 0x0585c7a9 in ~HttpServer? (this=0x8b75370, in_chrg=<value optimized out>) at httpserver.cpp:100 #8 0x0179f3ee in MythContextPrivate::DeleteUPnP (this=0x8b74068) at mythcontext.cpp:936 #9 0x0179eef8 in MythContextPrivate::InitUPnP (this=0x8b74068) at mythcontext.cpp:899 #10 0x017a17a6 in MythContextPrivate::DefaultUPnP (this=0x8b74068, error=...) at mythcontext.cpp:1130 #11 0x01798f29 in MythContextPrivate::FindDatabase? (this=0x8b74068, prompt=false, noPrompt=false)

at mythcontext.cpp:359

#12 0x01798df2 in MythContextPrivate::Init (this=0x8b74068, gui=false, UPnPclient=0x0, promptForBackend=false,

noPrompt=false, ignoreDB=false) at mythcontext.cpp:303

#13 0x017a4649 in MythContext::Init (this=0x8b73bd0, gui=false, UPnPclient=0x0, promptForBackend=false,

disableAutoDiscovery=false, ignoreDB=false) at mythcontext.cpp:1388

#14 0x0815bcd0 in setup_context (cmdline=...) at main_helpers.cpp:230 #15 0x08098270 in main (argc=7, argv=0xbfb31b84) at main.cpp:187

Change History (3)

comment:1 Changed 9 years ago by stuartm

Owner: changed from Isaac Richards to stuartm
Status: newaccepted

comment:2 Changed 9 years ago by anonymous

I recently upgraded my trunk installation to 25397. Since then (three days) I not only don't see any additional mythbackends, but the defunct mythfrontends have also disappeared. I haven't noticed anything in the commits that stands out to have solved this problem, but ...

You may close this ticket. I'll reopen if the problem re-occurs.

-- Ken E.

comment:3 Changed 9 years ago by stuartm

Resolution: invalid
Status: acceptedclosed

You probably updated QT at the same time, the problem was identified as a QT bug which was fixed in 4.6.x

Note: See TracTickets for help on using tickets.