Opened 16 years ago
Closed 15 years ago
Last modified 15 years ago
#9304 closed Bug Report (fixed)
[CRASH] mythcommflag random segfaults
| Reported by: | 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)
Change History (12)
by , 16 years ago
| Attachment: | commflag-run added |
|---|
by , 16 years ago
| Attachment: | 0001-Detect-null-frames.patch added |
|---|
comment:1 by , 16 years ago
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 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 16 years ago
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 by , 16 years ago
| Status: | assigned → infoneeded |
|---|
Is there any debugging information forthcoming? Closing this ticket Feb 28, 2011 if no more info is provided.
comment:5 by , 16 years ago
| Summary: | mythcommflag random segfaults → [CRASH] mythcommflag random segfaults |
|---|
comment:6 by , 15 years ago
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 by , 15 years ago
| Status: | infoneeded → assigned |
|---|
comment:8 by , 15 years ago
| Milestone: | → 0.25 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → 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 by , 15 years ago
| Milestone: | 0.25 → 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
commflag run with crash