Question by Elum224 · Aug 13, 2014 at 08:26 AM · java

How do I find out what is wrong in this stack trace?

This is the error report I'm getting from an app. java.lang.Error: FATAL EXCEPTION [UnityMain] Unity version : 4.5.2f1 Device model : LGE Nexus 4 Device fingerprint: google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000008 Build fingerprint: 'google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys' Revision: '11' pid: 22020, tid: 22061, name: Thread-730 >>> com.utilityfunction.roid <<< r0 00000000 r1 a448a108 r2 4009c384 r3 00000004 r4 00000011 r5 5170f2a8 r6 416ebdc0 r7 00000002 r8 416b3cac r9 517b8568 sl 00000000 fp 49fb8c60 ip 49fb8c50 sp 49fb8b18 lr 4163b76d pc 4160fe46 cpsr 753a3633

at libart.0016fe46(Native Method) at system@framework@boot.0001fca4(Native Method) at Object.runtime_invoke_virtual_void_this(Native Method) at Object.runtime_invoke_virtual_voidthis(Native Method) at libmono.0017bdd7(Native Method) at libmono.002cef7c(Native Method) at libmono.mono_gc_invoke_finalizers(mono_gc_invoke_finalizers:24) at libmono.0017e32c(Native Method) at libmono.00245d90(Native Method) at libmono.00299bd4(Native Method) at libmono.002e051c(Native Method) at libc.thread_entry(_thread_entry:72) at libc.pthread_create(pthread_create:240)

Add comment · Show 3

MrSteve1 · Aug 13, 2014 at 08:40 AM 0

and.......

Elum224 · Aug 13, 2014 at 11:10 AM 0

So far I know it is a memory access issue. Some of the usual causes for this are: Two threads trying to access the same memory, Trying to access memory you are not allowed, Null pointer exceptions.

I'm looking through my code for anything like that and I'm not finding anything. I'm wondering if there are any known Unity issues that cause this (or a combination of commands / objects that can cause the memory issue)