Sigbart 6 when setting datasource

wseemann / FFmpegMediaMetadataRetriever

FFmpegMediaMetadataRetriever provides a unified interface for retrieving frame and meta data from an input media file.

1.72k stars 387 forks source link

Sigbart 6 when setting datasource #203

Open Hackmodford opened 5 years ago

Hackmodford commented 5 years ago

Anything newer than version 10 causes a sigbart 6 when I try to set the datasource.

I'm trying to upgrade to the latest version to make sure my app support 64bit.

I'm not sure how to debug/fix this issue as it seems to be a bug in the C code. Is there anything I can do to give you more information?

Hackmodford commented 5 years ago

I am getting a sigbart -6

Using the context and uri gives me the error Using just the path gives me the error Removing whitespaces from path (in both cases) still gives error

Only reverting to 1.0.10 resolves the issue. Problem is, that version doesn't have 64 bit support.

Hackmodford commented 5 years ago

My fork of the project can be found here. https://github.com/Hackmodford/FFmpegMediaMetadataRetriever/tree/feature/arm64

Hackmodford commented 5 years ago

My prebuilt re-introduced issue #102 in API 19

wseemann commented 5 years ago

I already provide binaries for arm64-v8a, what was the point of this fork @Hackmodford ?

wseemann commented 5 years ago

Also, @Hackmodford please don't post native prebuilt binaries here. From a security perspective, it's not a good idea to encourage users to use random binaries.

wseemann commented 5 years ago

I'm trying to test the current version in a arm64-v8a device however it seems Google doesn't provide emulators for this anymore @Hackmodford ? What are you using for testing?

Hackmodford commented 5 years ago

@wseemann I apologize for posting the binaries.

I have an LG G5 I use for testing. More than willing to help you test this as this is an important component of my app.

wseemann commented 5 years ago

No worries, can you post a stack trace or anything I could use to debug the crash? I don't have a physical device to test on and it appears arm64 devices are deprecated.

On Mon, Jul 1, 2019 at 10:18 AM Brandon Butler notifications@github.com wrote:

@wseemann https://github.com/wseemann I apologize for posting the binaries.

I have an LG G5 I use for testing.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wseemann/FFmpegMediaMetadataRetriever/issues/203?email_source=notifications&email_token=AARQTBECC3CSHI3IHHHAE53P5I4ABA5CNFSM4HMSZ3G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6ZIOY#issuecomment-507352123, or mute the thread https://github.com/notifications/unsubscribe-auth/AARQTBAN4VW37JA2ZWKQV3TP5I4ABANCNFSM4HMSZ3GQ .

Hackmodford commented 5 years ago

2019-07-11 10:40:37.015 13880-14406/com.hughesmedia.big_finish A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 14406 (AsyncTask #4)

Yeah, I don't know if that is really helpful... I ran it again and got this.

2019-07-11 10:46:38.162 15420-15692/com.hughesmedia.big_finish D/BIGFINISH_TAG: analyzing track at path = /data/user/0/com.hughesmedia.big_finish/no_backup/756/Doctor Who - The Companion Chronicles - The Beginning/The Beginning.m4b
2019-07-11 10:46:38.163 15420-15692/com.hughesmedia.big_finish V/MediaMetadataRetrieverJNI: setDataSource

    --------- beginning of crash
2019-07-11 10:46:38.227 15420-15692/com.hughesmedia.big_finish A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 15692 (AsyncTask #4)