[FFmpeg-trac] #1876(avcodec:reopened): vc1dec.c multi-threading decode crash issue

[FFmpeg]

#1876: vc1dec.c multi-threading decode crash issue
-------------------------------------+------------------------------------
             Reporter:  DonMoir      |                    Owner:
                 Type:  defect       |                   Status:  reopened
             Priority:  important    |                Component:  avcodec
              Version:  unspecified  |               Resolution:
             Keywords:  vc1 crash    |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  1            |
-------------------------------------+------------------------------------

Comment (by cehoyos):

 Replying to [comment:24 DonMoir]:
 > By the way, I have many more things to do then dealing with ffmpeg.
 Guess what: You are not the only one.
 > Finding bugs in ffmpeg can take a lot of time. Reporting them sometimes
 takes even more time then it took to find them.
 I already told you numerous times: It is ok if you add an analysis to a
 report, it is not ok if the analysis replaces the actual report.
 > I could spend all the time working just with ffmpeg but I can't afford
 to do that.

 > It seems quite reasonable to me that if I point you to the actual bug
 which may have taken days to find, someone could spend an hour on it
 rather than wasting time on this ridiculous correspondence.
 Yes, I agree: Instead of sharing insults, please provide a little more
 information!
 And apart from that: What should the developer do this hour? Don't you
 think it would make much more sense to work on a ticket that contains all
 necessary information? Or one where the reporter makes us believe he is
 actually interested in helping?
 > You would need tools that can spin off multiple instances of a file in
 multiple threads and play them at the same time for this particular
 problem.
 Names?
 Links?
 > Even then it can be hard to reproduce. Sometimes I can get it to crash
 right away and sometimes not. But I can always get it to crash.
 Then please provide the backtrace when it crashes, consider reading
 http://ffmpeg.org/bugreports.html if you believe I invented the idea of a
 backtrace because you provide such useful reports.
 > Pretending my ass. The crash report is not very relevant but I don't
 expect you to understand that either.
 See above.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1876#comment:25>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker