therefore, my application began to randomly crash using Fatal Signal 11 (with random actions, some seem to do this more often than others, but I have not found the template yet). I have no idea why this was not done before, and my code did not change much and basically, the same code is great for my colleague. what am i tired of doing to fix this:
- Rebooting my machine.
- Triple check of everything in my code
- Run gradlew cleans and restores everything
- Checking the old version of VCS (I'm sure it works)
- Checking the old version from VCS for a completely new project
- Using different versions of android (4.1-4.3)
- Using different emulators (regular avd and genymotion)
Honestly, I have all of the ideas, there were no changes on my machine (not even Windows updates), no major changes to the code (and I tried to return only to be safe), no changes to the JVM, Android Studio there was no update, and the error was completely random.
thanks for any ideas ...
crash report:
.debug A/libc﹕ Fatal signal 11 (SIGSEGV) at 0x97e2c9c4 (code=2), thread 1768 (.smartpos.debug)
11-25 12:37:20.092 103-103/? I/DEBUG﹕ *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-25 12:37:20.092 103-103/? I/DEBUG﹕ Build fingerprint: 'generic/vbox86p/vbox86p:4.3/JLS36G/eng.buildbot.20131113.022613:userdebug/test-keys'
11-25 12:37:20.092 103-103/? I/DEBUG﹕ Revision: '0'
11-25 12:37:20.092 103-103/? I/DEBUG﹕ pid: 1768, tid: 1768, name: .smartpos.debug >>> .debug <<<
11-25 12:37:20.092 103-103/? I/DEBUG﹕ signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 97e2c9c4
11-25 12:37:20.196 103-103/? I/DEBUG﹕ eax 97e2c034 ebx b6191ccc ecx b8aea200 edx 00000264
11-25 12:37:20.200 103-103/? I/DEBUG﹕ esi a56b0b58 edi a56b0b58
11-25 12:37:20.200 103-103/? I/DEBUG﹕ xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
11-25 12:37:20.200 103-103/? I/DEBUG﹕ eip b60ae6fc ebp 97e2c000 esp bfe452e0 flags 00210282
11-25 12:37:20.200 103-103/? I/DEBUG﹕ backtrace:
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
11-25 12:37:20.200 103-103/? I/DEBUG﹕
update:
It seems that the problem is with x86 images (both AVD and genymotion), if I use the hand image, everything seems to work. I will try to dig deeper and report a bug when I have more time. at the moment it seems to me that I should be patient with slow images of slow hands: /
source
share