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.
_______________________________________________ Libav-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
