# Android error in memcpy, in /lib/arm64/libfmod.so
**URL:** https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421
**Category:** FMOD Engine
**Created:** [March 8, 2019, 9:34am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421 "2019-03-08T09:34:47Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [March 8, 2019, 9:34am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/1 "2019-03-08T09:34:47Z")
I use FMOD low level API in my Android app. I updated it to add 64 bit libraries, so I updated FMOD to latest version (1.10.11).
Now I’m receiving hundreds of error reports (in my Google Play console) with only this information:
```
pid: 0, tid: 0 >>> com.mycompany.myapp <<< backtrace:
#00 pc 000000000001c3c8 /system/lib64/libc.so (memcpy+88)
#01 pc 000000000003dfe0 /data/app/com.mycompany.myapp/lib/arm64/libfmod.so
```
Top devices with this issue are:
- OPPO A37f
- OPPO A3s (CPH1803)
- OPPO F9 (CPH1823)
- HUAWEI Y6 2018 (HWATU-QG)
- Galaxy S7 edge (hero2lte)
- And many more…
Is this a known issue?
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [March 15, 2019, 3:28am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/2 "2019-03-15T03:28:57Z")
Unfortunately we aren’t able to tell anything meaningful from that information alone.
If you were able to reproduce this while using the logging version of FMOD, you would get a lot more information on the cause of the problem.
---
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [March 15, 2019, 6:48am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/3 "2019-03-15T06:48:06Z")
I know there is not enough information. I tried to reproduce it, but I’m not getting the error on any of my devices.
I decided to remove 64 bit fmod library from my Android app (32 bit fmod library is working with no errors), at least until it’s required by Google. Maybe then the error is fixed.
---
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [July 19, 2019, 8:02am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/4 "2019-07-19T08:02:56Z")
I added 64-bit libs to my project, and I’m receiving the same native error logs I pasted in my first post. I tried to reproduce the error, but I’m not able to do so.
Running Android ndk tool “addr2line” it turns out that the error is happening in the `FMOD::getGlobals(FMOD::Global**)` method. Does it give you any clue about what is happening?
---
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [July 24, 2019, 7:24am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/5 "2019-07-24T07:24:47Z")
Anybody can help please? ☹
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [July 26, 2019, 2:14am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/6 "2019-07-26T02:14:38Z")
If you can use the FMOD logging libraries (eg. libfmodL.so), you should get much better callstacks and logging.
---
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [July 26, 2019, 7:30am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/7 "2019-07-26T07:30:53Z")
Thank you. I can use logging libraries, but the problem is that I cannot reproduce the problem. I only receive crash logs through Google Play Developer Console. In Android, where are these logs generated? Can I capture and send them back to me?
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [July 30, 2019, 6:27am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/8 "2019-07-30T06:27:59Z")
By default FMOD will output to the device console, you can change this but only when using the logging libraries, via [Debug\_Initialize](https://fmod.com/resources/documentation-api?version=2.0&page=core-api-common.html#debug_initialize). But without being able to reproduce the issue it is a bit difficult to debug.
---
### Author:  [@sviudes](https://qa.fmod.com/u/sviudes)
#### Post date: [July 30, 2019, 6:55am UTC](https://qa.fmod.com/t/android-error-in-memcpy-in-lib-arm64-libfmod-so/14421/9 "2019-07-30T06:55:07Z")
Thank you.
As you said, the problem is that I can’t reproduce the issue, so it’s very difficult to debug. Only a few users are having this problem, but I cannot contact them (I’m only receiving the error through Google Play Console).
So far, the only I know is that it’s happening with 64 bit version of FMOD, and in the `FMOD::getGlobals(FMOD::Global**)` method. The error is `signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)`