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

#9304 closed Bug Report (fixed)

[CRASH] mythcommflag random segfaults

Reported by: erikmbuh@… Owned by: beirdo
Priority: minor Milestone: 0.24.1
Component: MythTV - Mythcommflag Version: 0.24
Severity: medium Keywords:
Cc: Ticket locked: no

Description

This seems pretty similar to #8590... since updating to 0.24, commflag segfaults during the majority of runs. Repeated runs on the same file will sometimes complete successfully, and sometimes segfault. (same hardware has been stable for many months, and never displayed this issue before, so I'm fairly certain it's a new software problem).
Attached are an example manual run, and stacktrace from the corefile.
This is with atrpms build 0.24-252 on F13.

Attachments (3)

commflag-run (1.7 KB) - added by anonymous 3 years ago.
commflag run with crash
commflag-trace (50.9 KB) - added by anonymous 3 years ago.
stack trace from failed run
0001-Detect-null-frames.patch (879 bytes) - added by beirdo 3 years ago.

Download all attachments as: .zip

Change History (12)

Changed 3 years ago by anonymous

commflag run with crash

Changed 3 years ago by anonymous

stack trace from failed run

Changed 3 years ago by beirdo

comment:1 Changed 3 years ago by beirdo

Please try this patch. It seems that somehow, a null frame is being read. This patch rejects the null frame rather than trying to use it. The patch is against current trunk.

comment:2 Changed 3 years ago by beirdo

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

comment:3 Changed 3 years ago by erikmbuh@…

No luck there - applied that patch to 0.24-255 sources, rebuilt, and it's still segfaulting reliably. I'll try to get some more debugging in in the next week or two.

comment:4 Changed 3 years ago by beirdo

  • Status changed from assigned to infoneeded

Is there any debugging information forthcoming? Closing this ticket Feb 28, 2011 if no more info is provided.

comment:5 Changed 3 years ago by beirdo

  • Summary changed from mythcommflag random segfaults to [CRASH] mythcommflag random segfaults

comment:6 Changed 3 years ago by erikmbuh@…

It's still happening. I've gathered a new batch of logs and stuff, now against atrpms 0.24-266; logs, corefile, and an original videofile that's reliably crashing are at http://buh.org/files/mythcrash/

comment:7 Changed 3 years ago by robertm

  • Status changed from infoneeded to assigned

comment:8 Changed 3 years ago by Github

  • Milestone set to 0.25
  • Resolution set to fixed
  • Status changed from assigned to closed

Check for null frame buffers in commflag

Fixes #9304. I ran this several times against the example bad recording, and
it gets very spammy with "Unknown decoding errors", but carries on to
completion every time, no crash. Please reopen a new bug if this doesn't fix
the issue.

Changeset: 7338bd90c4ddf15a9531164799a593eede0680a5

comment:9 Changed 3 years ago by Github

  • Milestone changed from 0.25 to 0.24.1

Check for null frame buffers in commflag

Fixes #9304. I ran this several times against the example bad recording, and
it gets very spammy with "Unknown decoding errors", but carries on to
completion every time, no crash. Please reopen a new bug if this doesn't fix
the issue.
(cherry picked from commit 7338bd90c4ddf15a9531164799a593eede0680a5)

Changeset: 362d834c8ca8d3a4554536adb54e79bbcb41e5c8

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.