Invalid address passed to dlfree

Question

My app seems to be crashing "randomly" and I can't figure out why.

The logcat shows the following error:

A/libc(24298): invalid address or address of corrupt block 0x78366c48 passed to dlfree
A/libc(24298): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 24322 (AsyncTask #5)

Could this be something I am doing? Is it something wrong with Android?

I'm not really sure where to start looking for this at.

The person who is seeing this crash did tell me they have "a bad SD card and Verizon is telling me I need to put a new one in." That may or may not be relevant.

It's your application if you have some native (ndk) code in it or it is from a library you are using. It is very unlikely that you have found a strange bug in Android framework. You need to provide more information. — auselen, Aug 05 '14 at 22:54
try debugging native allocations https://source.android.com/devices/native-memory.html — sherpya, Aug 08 '14 at 00:14

score 25 · Answer 1 · edited May 23 '17 at 10:29

25

It's hard to solve this issue with no code to look at or any clue what the app is about, but I'll give you my guess what can cause the problem, and hopefully this will lead you in the right direction to solve this issue.

First of SIGSEGV, is a segmentation fault. Which in other words means that a memory access violation, trying to access memory which you are not allowed to. A likely cause of this is that you have ran out of memory, maybe because a memory leak or simply used up all memory. This can be caused by a bug you are using in a plugin that uses native C/C++ code through NDK.

The error code 0xDEADBAAD ("dead bad") is used by the Android libc abort() function when native heap corruption is detected.

In my opinion your best shot is to try and recreate the problem in the emulator or get hold of a device which can cause the problem and start debugging memory to get a hunch of the cause of this.

I would also recommend you to take a look at this SO question which has similar problems.

Good luck, solving the issue!

Best regards, Rawa

edited May 23 '17 at 10:29

Community

1
1

answered Aug 07 '14 at 23:18

Rawa

13,357
6
39
55

3

I had a similar problem with my android settings and some other apps. In the log file `/data/tombstones/tombstone_01` in the `stack:` section I found that an app (in my case 'macchanger') was causing the issue. I don't know, maybe that app is malicious but I was not expecting an app to reproducible crash other apps (kinda scary). – JepZ Jun 12 '17 at 21:16
1

@JepZ that was a life saver! My device crashed in the middle of updating an app, and was in a boot-loop since. Thanks to your comment I was able to figure what directory to remove (that app now existed twice, and the second instance was mentioned in every tombstone), and my device booted up fine again. – Izzy Nov 05 '17 at 01:28
@Rawa I have a similar crash happening, Please help me if you can I was able to get tombstone file as I can recreate it in Emulator too. https://stackoverflow.com/questions/47836896/signal-11-sigsegv-code-1-segv-maperr-fault-addr-0x7f4485ff1820 – pradex Dec 18 '17 at 22:53

Invalid address passed to dlfree

1 Answers1