Opened 13 years ago
Closed 12 years ago
#1122 closed defect (worksforme)
H264 interlaced multithreaded decoding artifacts
Reported by: | efenstor | Owned by: | |
---|---|---|---|
Priority: | important | Component: | avcodec |
Version: | git-master | Keywords: | h264 regression |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | yes | |
Analyzed by developer: | no |
Description
The problem described in the ticket #993 (http://ffmpeg.org/trac/ffmpeg/ticket/993) is back again. Present in 0.10.2 from https://launchpad.net/~jon-severinsson/+archive/ffmpeg and git as well.
Change History (6)
comment:1 by , 13 years ago
Component: | FFmpeg → avcodec |
---|---|
Keywords: | h264 regression added |
Reproduced by developer: | set |
Status: | new → open |
comment:2 by , 13 years ago
has anyone successfully git bisected this ?
what is the first known to be broken and last known to be working revission ?
comment:3 by , 13 years ago
I tested the following command line:
$ ffmpeg -threads n -i 00009.MTS -f framecrc -an out
For n==1, I get an identical out file trying several times, for n==7 I get a different out file on nearly every run on a (single-core SSE2) Pentium M with both git head and 18a7f74 (indicating that this may not be a regression or that I see a different problem).
I was unable to reproduce this issue on a Core-2 Duo.
comment:4 by , 13 years ago
On the box where it can be reproduced does it also happen with asm or optimizations disabled ?
all my tries to reproduce this have failed sofar, valgrind also shows nothing unusual
comment:5 by , 13 years ago
I am not completely sure yet, but after several tests it seems to me like in the version 0.10.3 the problem is gone. I can only hope it's a consequence of intentional eradication of the bug and not its elusive nature.
comment:6 by , 12 years ago
Resolution: | → worksforme |
---|---|
Status: | open → closed |
It appears noone can reproduce this anymore since 5 months so iam closing it. If someone can reproduce it please reopen and provide as much information valgrind/hellgrind as possible and test disable-asm disable-optimiztaion
thanks!
I was able to reproduce this with -threads 7:
After several tries, the output was different from "-threads 1".