Fatal signal 11 (SIGSEGV)

[ccoffey]

Hey guys,

I am 1 step away from completing my Rajawali Fragment tutorial.

Can some of you please try the following on your devices?
https://github.com/ccoffey/RajawaliExperiment

This works perfectly for me on my tablet (Samsung Tab 10.1, Android 4.0.4).
It also works perfectly on my phone (Samsung Galaxy Nexus, Android 4.2.1) until I rotate it into landscape mode, when I do this I get a Fatal signal 11 (SIGSEGV).

This is all I am getting on LogCat.

01-12 00:07:43.522: D/dalvikvm(10186): GC_EXPLICIT freed 1173K, 16% free 10134K/12060K, paused 2ms+2ms, total 36ms
01-12 00:07:43.780: A/libc(10186): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 10186 (awaliexperiment)
01-12 00:07:43.819: D/Rajawali(10186): Found Material Lib: camaro_mtl
01-12 00:07:43.819: D/Rajawali(10186): Parsing material: 01_-_Default_CMRO_TEX.TGA
01-12 00:07:43.866: D/dalvikvm(10186): GC_CONCURRENT freed 321K, 15% free 10325K/12060K, paused 2ms+2ms, total 21ms
01-12 00:07:43.866: D/dalvikvm(10186): WAIT_FOR_CONCURRENT_GC blocked 7ms

Whats even worse is if I add the below to MainActivity.java then I can cause some very odd behaviour.

@Override
public void onPause()
{
    super.onPause();

    right.mRenderer.clearChildren();
}

Have you guys seen something like this before? Not so sure that I am suppose to be able to effect the UI in this manor. Shouldn't Android protect against this sort of this?

[jayschwa]

Try commenting out the call to onSurfaceDestroyed() in RajawaliFragmentActivity.
https://github.com/MasDennis/Rajawali/blob/master/src/rajawali/RajawaliFragmentActivity.java#L175

This sounds like it could be related to #274.

[Davhed]

I've seen this UI rendering issue, it was in relation to the live wallpaper settings activity.

[ccoffey]

Thank you jay, this fixed my issue, everything is working perfectly now.

Is it really safe to comment out onSurfaceDestroyed() tho?

[jayschwa]

Is it really safe to comment out onSurfaceDestroyed() tho?

Not really. It recycles Bitmap objects. Memory consumption will grow with it commented out. Damned if you do and damned if you don't 😒

[MasDennis]

@ccoffey I've had the same issue in the Rajawali examples app. It was fixed by setting the application's hardwareAccelerated attribute to false in AndroidManifest.xml

    <application
        android:hardwareAccelerated="false"

[jwoolston]

@ccoffey & @MasDennis depending on what the app is doing, it might be better to leave application level acceleration enabled and simply disable it at the activity level that way other activities in the app can benefit from having it on.

[MasDennis]

@jwoolston you're right, this should be defined per activity.

[asrep]

This happened to me today. I notice that if i set the wallpaper and then go back to live wallpaper settings it pop this fatal singal and recreate the engine.. I think that adding android:hardwareAccelerated="false" to the settings activity solved it but i'm not sure

EDIT: adding it to the settings activity did solved it. I think it worth to mentioned it out to other people here

[jwoolston]

@MasDennis this is now resolved correct?

[jwoolston]

This should be fixed now. I have closed #276 and I am closing this issue for the same reason.

[jwoolston]

Please reopen this if more information becomes available.