Opened 9 years ago

Closed 8 years ago

#8282 closed defect (Works for me)

[CRASH] Mythtranscode segfaulting with multiple ways

Reported by: otto at kolsi dot fi Owned by: beirdo
Priority: minor Milestone: unknown
Component: MythTV - Mythtranscode Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I have a recording that causes mythtranscode to segfault apparently in different ways depending on the parameters.

I've attached three stacktraces:

  • gdb-nocutlist.txt which is while transcoding recording without cutlist
  • gdb-withcutlist.txt which is while transcoding recording with cutlist
  • gdb-localfile.txt which is while transcoding same MPG file directly with --infile option and without cutlist

From the stacktraces it looks like all these cases are crashing in different places.

Attachments (3)

gdb-nocutlist.txt (20.1 KB) - added by otto at kolsi dot fi 9 years ago.
gdb-withcutlist.txt (17.7 KB) - added by otto at kolsi dot fi 9 years ago.
gdb-localfile.txt (11.4 KB) - added by otto at kolsi dot fi 9 years ago.

Download all attachments as: .zip

Change History (7)

Changed 9 years ago by otto at kolsi dot fi

Attachment: gdb-nocutlist.txt added

Changed 9 years ago by otto at kolsi dot fi

Attachment: gdb-withcutlist.txt added

Changed 9 years ago by otto at kolsi dot fi

Attachment: gdb-localfile.txt added

comment:1 Changed 9 years ago by robertm

Owner: changed from Isaac Richards to Janne Grunau
Status: newassigned

comment:2 Changed 9 years ago by beirdo

Owner: changed from Janne Grunau to beirdo
Summary: Mythtranscode segfaulting with multiple ways[CRASH] Mythtranscode segfaulting with multiple ways

comment:3 Changed 8 years ago by beirdo

Status: assignedinfoneeded

Otto, are any of these repeatable with current code? If so, please post a new backtrace. Much of that code has been tweaked and massaged since the original report.

If I don't hear back by Apr 22, 2011, I'll consider this closed, and we can start afresh with new bug reports for what remains.

comment:4 Changed 8 years ago by robertm

Resolution: Works for me
Status: infoneededclosed

No response by requested deadline, please open new tickets with new backtraces as necessary.

Note: See TracTickets for help on using tickets.