Opened 10 years ago

Closed 9 years ago

#6854 closed defect (Unverified)

Backend deadlock in normal operation

Reported by: stuartm Owned by: beirdo
Priority: minor Milestone: 0.24
Component: MythTV - UPnP Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Found the backend had hung during the night. Backtrace attached. Only shows two threads which is odd and may in fact make the BT useless. I was unable to step through the first thread, it was just stuck at that point.

Attachments (1)

1529387.txt (24.2 KB) - added by stuartm 10 years ago.
Backtrace obtained by attaching to pid of hung process

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by stuartm

Attachment: 1529387.txt added

Backtrace obtained by attaching to pid of hung process

comment:1 Changed 10 years ago by anonymous

Have you tried using pstack on the backend when it is hung?

comment:2 Changed 10 years ago by danielk

Component: MythTV - GeneralMythTV - UPnP
Milestone: 0.22unknown
Owner: changed from Isaac Richards to dblain

The first thread in the backtrace is the one that appears hung, the second thread is waiting on the first to finish.

I'm doubtful there enough info to fix it for someone familiar with the UPnP code, so I'm changing the milestone to unknown. dblain or greg can close it if this is not fixable with this info.

comment:3 Changed 10 years ago by Shane Shrybman

That trace looks similar, if not identical, to a trace I get from the 2nd frontend started on a single system.

Steps to reproduce: start one frontend and let it idle, start another frontend and it often hangs on startup, then attach gdb to the second pid.

comment:4 Changed 9 years ago by robertm

Status: newassigned

comment:5 Changed 9 years ago by beirdo

Owner: changed from dblain to beirdo

comment:6 Changed 9 years ago by beirdo

Version: headTrunk Head

comment:7 Changed 9 years ago by beirdo

Milestone: unknown0.24
Resolution: Unverified
Status: assignedclosed

If this reoccurs, please open a new ticket. With all the changes in the past 13 months, I would doubt we can even recreate the precise symptoms.

Note: See TracTickets for help on using tickets.