Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#9500 closed Bug Report (fixed)

Segmentation Fault When mythfrontend Exits

Reported by: Bill Meek <keemllib@…> Owned by: beirdo
Priority: minor Milestone: 0.25
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by wagnerrp)

To duplicate: start the frontend, wait for a quiet log, exit. Starting, watching an entire program then exiting also caused the same failure (but the backtrace/fe.log are from the simple start/exit case.)

Also references: http://www.gossamer-threads.com/lists/mythtv/users/469002

MythTV Version   : v0.25pre-924-g4e53b23
MythTV Branch    : master
Network Protocol : 64
Library API      : 0.25.20110119-1
QT Version       : 4.7.0

Attachments (4)

backtrace.txt (28.2 KB) - added by Bill Meek <keemllib@…> 3 years ago.
mythfrontend.log (27.2 KB) - added by Bill Meek <keemllib@…> 3 years ago.
fe.log (190.6 KB) - added by Bill Meek <keemllib@…> 3 years ago.
Correct FE log, disragard previous mythfrontend.log attachment
fe-v-extra.log (8.3 KB) - added by Bill Meek <keemllib@…> 3 years ago.
mythfrontent -v extra log

Download all attachments as: .zip

Change History (9)

Changed 3 years ago by Bill Meek <keemllib@…>

Changed 3 years ago by Bill Meek <keemllib@…>

Changed 3 years ago by Bill Meek <keemllib@…>

Correct FE log, disragard previous mythfrontend.log attachment

comment:1 Changed 3 years ago by mdean

  • Owner set to beirdo
  • Status changed from new to assigned

comment:2 Changed 3 years ago by beirdo

Actually, a more useful log would be from:
mythfrontend -v extra

What I want to see is the opening and closing of the threads as they are used, following by the death on quitting.

Changed 3 years ago by Bill Meek <keemllib@…>

mythfrontent -v extra log

comment:3 Changed 3 years ago by beirdo

  • Milestone changed from unknown to 0.25
  • Resolution set to Fixed
  • Status changed from assigned to closed

Fixed in 255a074b19a. I can no longer get it to crash in this way.

comment:4 Changed 3 years ago by Gavin Hurlbut

  • Resolution changed from Fixed to fixed

Change ThreadPool? shutdown to use deleteLater

This is to fix #9500, which has the frontend segfaulting on shutdown. This
code will hopefully all be overhauled in the awaited webserver rewrite, but
in the mean time, let's have it behaving.

I also moved the order of removing from the deque and marking it for deletion,
as I was toying with different locking methods.

Changeset: 255a074b19a9c72ee91a6028efe195d723854cf8

comment:5 Changed 3 years ago by wagnerrp

  • Description modified (diff)

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'new'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.