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

#9634 closed Bug Report - Crash (Unverified)

[CRASH] segfault in ImageLoadThread::run

Reported by: brian@… Owned by: beirdo
Priority: blocker Milestone: unknown
Component: MythTV - User Interface Library Version: 0.24-fixes
Severity: high Keywords:
Cc: Ticket locked: no

Description

Using 0.24-fixes from today, I am getting a pretty consistent segfault trying to start viewing a particular program.

The stack trace of the active thread in gdb when it segfaults:

#0  0x0a5e2e60 in ?? ()
#1  0x0053f0b3 in ImageLoadThread::run (this=0xb3cf790) at mythuiimage.cpp:104
#2  0x01a6625c in QThreadPoolThread::run (this=0x9bffa58) at concurrent/qthreadpool.cpp:106
#3  0x01a7132e in QThreadPrivate::start (arg=0x9bffa58) at thread/qthread_unix.cpp:248
#4  0x018e596e in start_thread (arg=0xa9bdfb70) at pthread_create.c:300
#5  0x01e72a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

I will attach the full threaded backtrace.

Attachments (1)

ThreadStacktrace.txt (97.1 KB) - added by brian@… 3 years ago.
threaded back trace of crash

Download all attachments as: .zip

Change History (15)

Changed 3 years ago by brian@…

threaded back trace of crash

comment:1 Changed 3 years ago by cpinkham

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

comment:2 Changed 3 years ago by beirdo

  • Owner changed from cpinkham to beirdo
  • Status changed from assigned to accepted
  • Version changed from Unspecified to 0.24-fixes

comment:3 Changed 3 years ago by Github

  • Milestone changed from unknown to 0.25
  • Resolution set to fixed
  • Status changed from accepted to closed

Initialize the MythUIImage filename correctly

Fixes #9634. Fixes #9708. Refs #9547.

If the filename does not start with "/", "http://", "https://" or "ftp://", then
the actual filename loaded is uninitialized. It can be any random crap on the
stack. I'm honestly surprised this worked at all :)

This may fix things for #9547 as well, and should be tested with that
scenario too.

Branch: master
Changeset: 2c7735e7f80b5d2737d2bc8c4e9144f3e42da2e7

comment:4 Changed 3 years ago by beirdo

  • Milestone changed from 0.25 to 0.24.2

comment:5 Changed 3 years ago by beirdo

  • Milestone changed from 0.24.2 to unknown
  • Resolution fixed deleted
  • Status changed from closed to new

It's worth trying the re-fixed code, but the above commit got reverted.

comment:6 Changed 3 years ago by beirdo

  • Priority changed from blocker to major

comment:7 Changed 3 years ago by beirdo

  • Summary changed from segfault in ImageLoadThread::run to [CRASH] segfault in ImageLoadThread::run

comment:8 Changed 3 years ago by beirdo

  • Status changed from new to infoneeded_new

Is this still happening in the particular test case that was cited in the ticket?

comment:9 Changed 3 years ago by stuartm

  • Component changed from MythTV - General to MythTV - User Interface Library
  • Milestone changed from unknown to 0.25
  • Priority changed from major to blocker

See also #9388

comment:10 Changed 3 years ago by beirdo

See also #9547

comment:11 Changed 3 years ago by beirdo

  • Milestone changed from 0.25 to unknown

I'm removing the milestone as it is not clear that this will be fixed with no input from affected users. When we get more input, it can be set at that time.

comment:12 Changed 3 years ago by beirdo

We need either a test case that allows us to reproduce this, or to have someone who is affected to work with us. This is a serious bug, but we are not being able to move forward on it. To the original poster: Is this still happening? Have you tried master (0.25-pre)?

comment:13 Changed 3 years ago by brian@…

I have not seen it in a while. I am also on master now though.

comment:14 Changed 3 years ago by beirdo

  • Resolution set to Unverified
  • Status changed from infoneeded_new to closed

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.