[Libav-user] av_parser_iterate crash

Landry Norris landry.norris0 at gmail.com
Tue Nov 8 17:36:41 EET 2022


I am unable to replicate this on a dev machine. Sadly, this means I don't
have useful logs, just a stacktrace. I've been trying
to check the source code to see where it could possibly be calling abort. I
don't see anything in av_parser_iterate in the
source. Is there something I should try to increase the chances of this
occurring? Since I don't have logs, I don't expect to
get a direct answer on how to solve this, but is there a direction I should
be looking?

Here is the stacktrace I see in Crashlytics for reference
__pthread_kill + 8
pthread_kill + 208
abort + 124
av_parser_iterate + 84732
and my code is below this in the stacktrace

Interestingly, I don't directly call av_parser_iterate, but instead I call
av_read_frame. Not sure if there's an issue with crashlytics here.

Landry Norris

On Mon, Nov 7, 2022 at 10:08 AM Nicolas George <george at nsup.org> wrote:

> Landry Norris (12022-11-07):
> > When running on iOS, I get crash reports from Crashlytics indicating a
> > SIGABRT inside of av_parser_iterate (I call av_read_frame, which calls
> > av_parser_init, which calls av_parser_iterate). The source for
> > av_parser_iterate doesn't directly call libsystem_c.dylib abort(), but I
> > think that iOS calls into this when bad memory is accessed.
> >
> > Has anyone run into this before, or is there a good place for me to start
> > looking for what the issue could be? I haven't been able to replicate
> this
> > on a dev machine. Reports just come in from crashlytics.
> A SIGABRT is usually the result of an assert failure. That means you
> should have all you need to know what happens in the log output.
> If not, attach the binary in a debugger and request a stack trace when
> you get the signal.
> Regards,
> --
>   Nicolas George
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/libav-user
> To unsubscribe, visit link above, or email
> libav-user-request at ffmpeg.org with subject "unsubscribe".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ffmpeg.org/pipermail/libav-user/attachments/20221108/ceecf9d7/attachment.htm>

More information about the Libav-user mailing list