Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1) - PhoneGap

47

I develop Android apps now with PhoneGap. Lately when I try to switch between HTML pages, the application closed, and in the LogCat the following error appears:

12-24 15:43:39.237: A/libc(23631): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 23631 (.example.app)

I searched a bit on Google about this error, and what I understand is that it is related to the device's memory. I found some solutions, but not so much that I realized how I implement them in PhoneGap.

Has anyone here encountered this error before? What can I do to solve the problem?

Thank you :)

java
android
eclipse
cordova
asked on Stack Overflow Dec 24, 2012 by Yehuda

9 Answers

44

If you have written (or are using) a plugin that in turn uses native C/C++ code through the NDK, this may indicate a bug in that native code.

Otherwise, this is a bug in the firmware of the device or emulator you are testing upon.

If you can reproduce this in an emulator, on a Nexus device with the original ROM, or on a variety of devices from different manufacturers, it is probably a bug in Android itself. In that case, please create a sample project that can reproduce the error, and post it along with the entire stack trace to http://b.android.com, the Android OS issue tracker.

If you are only encountering this on one device or one third-party ROM, it is probably a more specific bug -- your best bet is to contact the device manufacturer or ROM publisher with your symptoms.

answered on Stack Overflow Dec 24, 2012 by CommonsWare • edited Oct 5, 2014 by Tash Pemhiwa
16

I was getting a similar error on the xhdpi Nexus 7 but things worked fine on my old phone. My problem occurred while updating a large GridView with lots of small buttons.

A/libc(7410): Fatal signal 11 (SIGSEGV) at 0xbe8a8000 (code=1), thread 7410

I don't think this is your problem because your PC was 0 and mine was at 0xbe8a8000 but it's easy to try and it fixed my problem so I'm going to post it in case someone else comes here looking for a SEGV solution.
There was a discussion on https://github.com/MasDennis/Rajawali/issues/313 about a similar problem and someone mentioned that they had the same problem and turning off hardware acceleration fixed it for them. It's easy to try and it fixed my problem.
In the Android manifest application add:

android:hardwareAccelerated="false"

Hope this helps someone else...

answered on Stack Overflow Jan 6, 2015 by steven smith
11

I just had the same problem on a project I was working on. It turned out that I was loading a lot of images and sounds and causing the app to run out of memory while trying to instantiate an Activity. Does your program use a lot of memory-intensive assets? Can you reduce their sizes at all?

In my case, the LogCat had a stack trace in green (INFO-level logging) immediately before the Fatal signal 11 (SIGSEGV) line. The stack trace was an OutOfMemoryException while the app was loading assets for an Activity I was starting up. So I pulled up my drawables (my program had a lot of them), edited them to reduce their file size, and tried again. The bug went away. You can see if your LogCat output looks like mine to see if you have a similar issue:

01-15 05:20:40.462: E/dalvikvm-heap(4513): Out of memory on a 3145744-byte allocation.
01-15 05:20:40.462: I/dalvikvm(4513): "main" prio=5 tid=1 RUNNABLE
01-15 05:20:40.462: I/dalvikvm(4513):   | group="main" sCount=0 dsCount=0 obj=0x4158b6a0 self=0x41001a60
01-15 05:20:40.462: I/dalvikvm(4513):   | sysTid=4513 nice=0 sched=0/0 cgrp=apps handle=1074673744
01-15 05:20:40.462: I/dalvikvm(4513):   | schedstat=( 0 0 0 ) utm=41 stm=20 core=1
01-15 05:20:40.462: I/dalvikvm(4513):   at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
01-15 05:20:40.462: I/dalvikvm(4513):   at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:592)
01-15 05:20:40.462: I/dalvikvm(4513):   at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:445)
01-15 05:20:40.462: I/dalvikvm(4513):   at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:781)
01-15 05:20:40.462: I/dalvikvm(4513):   at android.content.res.Resources.loadDrawable(Resources.java:1963)
01-15 05:20:40.462: I/dalvikvm(4513):   at android.content.res.Resources.getDrawable(Resources.java:672)
01-15 05:20:40.462: I/dalvikvm(4513):   at com.kbi.speeddraw.lite.game.drawables.character.ExplodingCharacterDrawable.<init>(ExplodingCharacterDrawable.java:27)
<!-- snip -->
01-15 05:20:40.462: I/dalvikvm(4513):   at com.kbi.gameengine.api.gameactivity.GameActivity.onCreate(GameActivity.java:80)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.Activity.performCreate(Activity.java:5048)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2052)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2113)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.ActivityThread.access$700(ActivityThread.java:139)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1224)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.os.Handler.dispatchMessage(Handler.java:99)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.os.Looper.loop(Looper.java:137)
01-15 05:20:40.472: I/dalvikvm(4513):   at android.app.ActivityThread.main(ActivityThread.java:4918)
01-15 05:20:40.472: I/dalvikvm(4513):   at java.lang.reflect.Method.invokeNative(Native Method)
01-15 05:20:40.472: I/dalvikvm(4513):   at java.lang.reflect.Method.invoke(Method.java:511)
01-15 05:20:40.472: I/dalvikvm(4513):   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1004)
01-15 05:20:40.472: I/dalvikvm(4513):   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:771)
01-15 05:20:40.472: I/dalvikvm(4513):   at dalvik.system.NativeStart.main(Native Method)
01-15 05:20:40.472: A/libc(4513): Fatal signal 11 (SIGSEGV) at 0x00000be0 (code=1), thread 4513 (.speeddraw.lite)
01-15 05:20:40.472: A/libc(4513): Fatal signal 11 (SIGSEGV) at 0x00180500 (code=1), thread 4527 (.speeddraw.lite)
answered on Stack Overflow Jan 15, 2013 by Kevin
4

Check for OutofMemory issues in my case I got this error on Samsung S3 and was for managing a lot of images on startup Activity. I googled a lot of responses without a solution because I didn't have an EditText or an input at all (actually, I don't know why the error show the spannable string zero lenght..... and not another thing like OutOfMemory, etc), then I realize the images ordered by resolution were in the wrong folders and oversized, and the Heap up in the skies. Good Luck

answered on Stack Overflow Oct 30, 2013 by Ciclids • edited May 5, 2019 by recnac
4

The following Google Plus post fixed my problem:

Basically the problem is related to optical bounds in 9 patches files. In my case I was using newer 9patches copied from the Holo Theme. This new patches are invalid in older versions of android as explained in the link

answered on Stack Overflow Mar 26, 2014 by unify • edited Apr 28, 2014 by GVillani82
3

Make sure you have all the resources images under assets directory. I had this problem and it turns out that one of my images is missing. Once I put the image back under assets directory, everything is fine.

answered on Stack Overflow Apr 11, 2013 by Emmy
1

use this one... options.headers = { "Connection":"close" };

answered on Stack Overflow Jun 6, 2014 by mahi
0

The following worked for me to get rid of the error in the webview:

webView.freeMemory();

or

webView.clearCache(true);

The second option will slow down your app.

answered on Stack Overflow Jun 13, 2016 by user3727574 • edited Jun 13, 2016 by buczek
0

For me issue is in chrome webview. I disable chrome & enable Android webview. It works fine for me.

answered on Stack Overflow Dec 26, 2019 by Rajan Kashiyani

User contributions licensed under CC BY-SA 3.0