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

Question

Now I am developing Android applications using PhoneGap. Recently, when I try to switch between HTML pages, the application closes and the following message appears in LogCat:

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

I searched Google a little for this error, and I understand that it is related to the device’s memory. I found some solutions, but not so much that I understood how I implement them in PhoneGap.

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

Thank:)

Answer 1

If you wrote (or use) a plugin that, in turn, uses its own C / C ++ code through the NDK, this may indicate an error in this native code.

Otherwise, it is an error in the firmware of the device or emulator that you are testing.

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

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

Answer 2

I was getting a similar error on xhdpi Nexus 7, but everything worked fine on my old phone. My problem occurred while updating a large GridView with many 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 computer was 0 and mine was on 0xbe8a8000, but it was easy to try and it fixed my problem, so I am going to publish it in case anyone else comes here to search SEGV solution.
The issue of https://github.com/MasDennis/Rajawali/issues/313 about a similar problem was discussed, and someone mentioned that they had the same problem, and disabling hardware acceleration was fixed for them. It is easy to try and it fixed my problem.
In the Android manifest application, add:

 android:hardwareAccelerated="false" 

Hope this helps someone else ...

Answer 3

I had the same problem in the project I was working on. It turned out that I load a lot of images and sounds and make the application work without memory when trying to create an instance of Activity. Does your program use a lot of memory intensive resources? Can you reduce their size at all?

In my case, LogCat had a stack trace in green (registering the INFO level) immediately before the Fatal signal 11 (SIGSEGV) . The stack trace was an OutOfMemoryException , while the application was loading assets for the Activity that I was running. So I pulled up my drawings (there were a lot of them in my program), edited them to reduce the size of their files, and tried again. The error has disappeared. You can see if your LogCat output looks like mine to see if you have a similar problem:

 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) 

Answer 4

Checking for OutofMemory problems in my case, I got this error on Samsung S3 and was for managing a lot of images when starting Activity. I googled a lot of answers without a solution, because I didn’t have EditText or input at all (in fact, I don’t know why the error shows that the line with the ability to put down is zero ..... and not another thing, like OutOfMemory and etc.), then I understand that the images, ordered by resolution, were in the wrong folders and oversized, and a bunch in the sky. Good luck

Answer 5

The following Google Plus mail fixed my problem:

Mostly the problem is with the optical borders in 9 patch files. In my case, I used more than 9 copies copied from the Holo theme. These new fixes are not valid in older versions of android, as described in the link

Answer 6

Make sure you have all the resource images in the resource directory. I had this problem and it turned out that one of my images is missing. After I returned the image to the resource directory, everything is in order.

Answer 7

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

Answer 8

The following steps helped me get rid of a webview error:

 webView.freeMemory(); 

or

 webView.clearCache(true); 

The second option will slow down your application.