TOPIC:

I've been receiving various reports and reproducible issues from our users where a SIGSEGV or other fatal signal occurs in native code in PDF Viewer SDK and crashes our app. I will post these issues individually in other threads.

The problem is that when a signal occurs, the app crashes and we don't get notified of the crash since it happened in native code and the process dies. It would be extremely helpful if you would add signal handlers to catch SIGSEGV and other fatal signals and throw Exceptions in Java when they occur with proper stack traces and relevant data. This way we will at least get notified when crashes occur and we can provide you with the relevant information to fix the issues.

There is a great post about how to catch signals and throw Java Exceptions here: blog.httrack.com/blog/2013/08/23/catchin...-signals-on-android/

Please let me know if you have any questions.

Thanks,
Andrew

Hi,
check the new library version www.radaeepdf.com/forum/roadmap-and-rele...df-viewer-sdk-3-3-11

Does this new SDK version catch native crashes and throw them as Java Exceptions? The changelog doesn't mention anything about it.

Thanks,
Andrew

It would be extremely helpful if the native library could catch the native crashes and throw them as Java Exceptions. We keep getting reports of native crashes such as SIGSEGV. If we could catch these in Java as Exceptions, then we can have more context as to when they are occurring and can report them to you easier (with more relevant information), as well as recover gracefully instead of letting the app crash entirely.

Here is a library that should help in doing this: github.com/xroche/coffeecatch

Please let me know if you have any questions.

Thanks,
Andrew

Right now we was focused in improving and fixing 64 bit architecture and overall stability, then we introduced the Javascript support.
We're really interested in your suggestion and we will take in charge as soon as possible.

Note: we should find the best multiplatform approach that would allow us to support at least Android and iOS (better if windows could be supported too).

The dev team is aware about your note. I'll give you a complete feedback as soon as possible.

Thanks! Looking forward to it.