[mythtv-commits] Ticket #2438: Infinite loop in mythbackend

MythTV mythtv at cvs.mythtv.org
Thu Oct 12 16:42:08 UTC 2006


#2438: Infinite loop in mythbackend
---------------------------------------+------------------------------------
 Reporter:  ian at beware.dropbear.id.au  |        Owner:  cpinkham
     Type:  defect                     |       Status:  new     
 Priority:  minor                      |    Milestone:  unknown 
Component:  mythtv                     |      Version:  0.20    
 Severity:  high                       |   Resolution:          
---------------------------------------+------------------------------------
Comment (by thetaz):

 Sorry, I don't read -dev at all, but yes..

 I have a linksys WRT54G router with custom firmware that has uPnp turned
 on.  This is the only device that has it turned on when this is happening.
 It seems like this is happening when I do not have any other computers or
 devices turned on that are connected to my WRT54G switch.  Ie, I will have
 mythbackend at 0% cpu usage when going to sleep, shut down all
 devices/systems then wake up in the morning at mythbackend is cycling at
 99.9% cpu.  Mythbackend will still allow me to connect so it seems like it
 is a thread.  Therefore, it may be possible that the router is sending a
 packet out to the network that is triggering the uPnp on my backend.  The
 branch I'm using is .20-fixes but I see that the other branch has a
 --noupnp option so I will compile that and run it with that option to see
 if my results improve.

 I also ran opannotate after I had left oprofile running for a couple of
 days and allowed the backend to loop for over a day at 100% cpu, I will
 attach a copy of the summary output to this ticket but it looks like it is
 in fact using a lot of cycles in the uPnp feature.

 Thanks

-- 
Ticket URL: <http://cvs.mythtv.org/trac/ticket/2438#comment:17>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list