Opened 10 years ago

Closed 8 years ago

#9600 closed Bug Report - Hang/Deadlock (Need more Info)

Frontend hang when entering recordings screen

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

Description

Looks like this might be it?

QThread::start: Thread creation error:

Attachments (3)

strace.log (128.3 KB) - added by Marc Randolph <mrand@…> 10 years ago.
gdb.txt (33.3 KB) - added by Marc Randolph <mrand@…> 10 years ago.
mythfrontend.log (103.9 KB) - added by Marc Randolph <mrand@…> 10 years ago.

Download all attachments as: .zip

Change History (8)

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

Attachment: strace.log added

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

Attachment: gdb.txt added

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

Attachment: mythfrontend.log added

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

Sorry, I didn't describe the hang very well...

The recordings look to all be displayed, and then there is the "Loading..." pop-up on top of that, and the clock keeps going around, and around, and around.

comment:2 Changed 10 years ago by beirdo

Looking further up in the log shows a LOT of mmap errors indicating the machine is out of memory, or so it seems. How much memory, how much swap?

comment:3 Changed 10 years ago by Marc Randolph <mrand@…>

System has 2 GB of memory with 2 GB of swap.

That log was immediately after a fresh reboot of the FE + BE with no other applications running to speak of except the nvidia-settings, which is still running and only consuming 66 MB. It looks like those messages were during a trail viewing of a DVD. If the system really was low on memory during that time period, it was myth's doing. Is that message trust-worthy?

comment:4 Changed 9 years ago by beirdo

Type: Bug Report - GeneralBug Report - Hang/Deadlock

comment:5 Changed 8 years ago by beirdo

Resolution: Need more Info
Status: newclosed

Is this still an issue with 0.25 or master? If so, please reopen the ticket. Enough has changed in the last 17 months that I doubt this is still valid at this point.

Note: See TracTickets for help on using tickets.