[FFmpeg-trac] #1863(undetermined:closed): Remove all abort() calls from ffmpeg libraries
FFmpeg
trac at avcodec.org
Mon Nov 12 23:28:13 CET 2012
#1863: Remove all abort() calls from ffmpeg libraries
-------------------------------------+-------------------------------------
Reporter: DonMoir | Owner:
Type: defect | Status: closed
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: | Resolution: wontfix
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by DonMoir):
The problem is in a GUI app it's plain ridiculous. No one knows why it
suddenly shut down and then you have people chasing ghosts. Also in my
case, the GUI app is doing a lot more then just playing a video. It's also
running laser shows etc. in public view. Why shut the whole program down
when just one video or whatever failed ?
We now might have a laser stuck on hold shooting airplanes out of the sky.
(just kidding)
When I first found this it was one of those spurious crashes from the
unmentionable ticket #1876 and so was busy looking at that. I ignored it
because I knew it was just a random crash due to the nature of threading
but it made me aware of the abort calls.
In the real world we need to be more accountable for problems such as
these.
There is enough justification in this ticket to have a closer look. If
only one video failed, then so what. It's not justification to shut the
whole program down.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1863#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list