Fatal signal 11 during native Android code execution

Question

Java

Good day!
At the moment I am developing an application for Android, and about half of the logic in it is written in C ++. The application is finished, but when run on samsung galaxy nexus it sometimes crashes with Fatal Signal 11 error (as tag is given by libc). As I understood from a Google search, this is the same segmentation fault. The problem is that the error appears periodically, sometimes it may not appear for two hours, sometimes at the first start, and sometimes the application crashes every time.
At the very least, I found the problematic line of code, but it is not clear what is wrong with it, and why the problem does not always occur.
My question is, has anyone experienced this problem? It is with periodic loss? If so, what are the ways to deal with it?
Thanks in advance.

PS In the question, I did not specifically indicate anything specifically about the program, if accurate information is needed, I will write below. There may just be some common causes and solutions to this problem ...

Answer 1

It is very similar to a flight with a multi-threaded application (it may not appear at all during debugging / emulation). For example, one thread holds the pointer, the second one crashes it, the first thread is not aware of this - that's sigsegv.
If the application is really multi-threaded, look towards synchronization primitives (mutexes, semaphores, etc.).
And of course, it’s hard to say without code ... Maybe some kind of system error, or some kind of library fails.