Multiple SIGABRT crash reports during decoding phase
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 255
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
We have about 500 crash reports per month, which are difficult to reproduce. Can you please review the attached stacktrace and throw Java Exception instead of crash? Thank you in advance.
```
SIGABRT Abort program
/apex/com.android.runtime/lib/bionic/libc.so:392370 abort
/apex/com.android.runtime/lib/bionic/libc.so:393739 __assert2
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:208563 0xaa38eeb3
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:208821 0xaa38efb5
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:202099 0xaa38d573
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:200227 __cxa_get_exception_ptr
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:200171 __cxa_throw
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:192599 operator new(unsigned int)
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:105311 0xaa375b5f
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:105215 apng_drawable::ApngFrame::ApngFrame(unsigned int, unsigned int)
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:98233 apng_drawable::ApngDecoder::decode(std::__ndk1::unique_ptr >, int&)
/data/app/com.photo.app-u2VLzjwd7M7a7x8Ch8Rd4A==/lib/arm/libapng-drawable.so:100223 Java_com_linecorp_apng_decoder_ApngDecoderJni_decode
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ApngDecoder::decode and Java_com_linecorp_apng_decoder_ApngDecoderJni_decode entry points shown in the stack trace, then trace how decoding failures cross the JNI boundary. The issue is complete when the reported decoding failure produces a Java exception instead of SIGABRT; no test or reproduction steps are provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100