"Fatal signal 11" in native blur

[JoanZapata]

Hi,

Thank you for this great lib, the java version is working very well, but I tried the native version and I got a libc﹕Fatal signal 11 (SIGSEGV) at 0x62448000 (code=2), thread 30186 (AsyncTask #3), which makes the app the shutdown immediately.

I'm really new to the NDK, from what I understand with Google it could be anything, so I'm not asking for a solution but I'm trying to see if I missed something. :)

• I made sure the native code is only running in one thread, so it's not a concurrent access problem.
• I can see the native logs in the logcat: Image size is: 640 680, so far so good…
• I've put some logs in the loops of the algorithm, and from what I can see, the crash is occuring at random points during the algorithm. If I put "return;" at the beginning of the native function the app doesn't crash (but no blur, of course).

Do you have any pointer on this? I run the code in an AsyncTask, is it wrong?

Thank you for your time and keep up the good work!

[kikoso]

Hello @JoanZapata ,

SIGSEV is really hard to track. Your application is accessing memory outside of its address space (SIGSEGV = segmentation fault in native code)

You will not be able to see a Logcat stack trace, but you might get some clues after the application crashes if you look carefully. You can also set up a gdb native bridge and catch it on the debugger.

However happens, let me know. I am trying to reproduce it, but I am not able to do it. Have you tried with different devices?

Regards

[kikoso]

Hello @JoanZapata ,

There is a new release with this bug fixed thanks to @Dr-Emann . Please, check it out :-).

Regards

[JoanZapata]

That's really really good news thank you, I'll test it probably tomorrow and let you know! :-)