Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1). How can it be tracked down?

后端 未结 24 975
遥遥无期
遥遥无期 2020-11-22 08:33

I\'ve been reading the other posts on tracking down the reasons for getting a SIGSEGV in an Android app. I plan to scour my app for possible NullPointers relate

24条回答
  •  隐瞒了意图╮
    2020-11-22 09:04

    I faced this issue moment ago, after migrating from android.support to androidx.

    The problem was renderscript.

    Solution: I removed from my build.gradle those two lines:

    renderscriptTargetApi 21
    renderscriptSupportModeEnabled true
    

    after that project building failed, because of unresolved references:

    import androidx.renderscript.Allocation;
    import androidx.renderscript.Element;
    import androidx.renderscript.RenderScript;
    import androidx.renderscript.ScriptIntrinsicBlur;
    

    so I've changed them to:

    import android.renderscript.Allocation;
    import android.renderscript.Element;
    import android.renderscript.RenderScript;
    import android.renderscript.ScriptIntrinsicBlur;
    

    After that all problems were gone.

提交回复
热议问题