IssueTracker

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

We are not able to reproduce the issue with Android emulator with Nexus 5 with  Android 6.0.1

As you mentioned in comment #1 please provide the bugreport and video for  Nexus 5 with  Android 6.0.1

@2 Sadly the Nexus 5 was upgraded recently to have a custom ROM with newer Android version. The bug did exist there before I've reported the current issue (on the previous issue I've reported about).
The other devices haven't though. And, you can get the bug report file from the other issue I've written about, of the same device, here (just of older support library version) :
https://issuetracker.google.com/issues/64431012#comment8

Also, as I wrote, I failed to reproduce it on emulators.
Please try on any of the other devices.

Here, attached APK to try it out.

@2 Attached bug report of Nexus 4 with 5.1.1 (LMY48T).
As I wrote, it occurs there too, but for some reason not on 4.4.4 .

I can easily reproduce it on LG G3 (Android 5.0) and Samsung Galaxy S7 (Android 7.0) with attached sample application. Actually this issue is the only reason I can't upgrade from 25.3.1 (tried every release but then rolled back) as workarounds suggested in the initial issue help to suppress crash but ruin user experience.

Initially it was hard to make it crash so I have even created my own example but then I found quick way to reproduce the issue: fling content to the top and then drag it down straight away. 99% of times app crashes immediately and if it doesn't crash then you should do it again, probably a bit faster.

I'm attaching my example anyway as well as captured video, verbose application log and apk itself.

We have shared this with our engineering team and will update this issue with more information as it becomes available.

I have the same issue too.

Any update on the issue? Support library brings more and more fantastic updates but I can't upgrade because of this issue.

Is it possible to at least raise priority and/or severity? There are plenty of trash P3 issues while this one, which holds upgrade to newer support libraries, is just a P4.

@9 Is P1 the top priority?

@10 I believe so.

@11 OK. Thanks.

Any update on this please?

Feb 9 this went into the void ...

I have the same issue on Samsung Galaxy S6 Android 6.0.1. Support library version 27.0.2.
Any plans to fix it?

assignee changed due to member moving out of team.

We will be closing this bug as Obsolete. If you still think this issue is reproducible and relevant in the latest Android release (Android Q), please attach a new bug report along with reproduction details. If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.

Yes, it's a duplicate anyway of something that I think was fixed:
https://issuetracker.google.com/issues/69593710

I have the same issue on Samsung Galaxy S9 Android 8.0. Support library version 27.0.2.
Any plans to fix it?

Native crash of com.sec.android.inputmethod
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/starqlteue/starqlteue:8.0.0/R16NW/G960U1UEU1ARBG:user/release-keys'
Revision: '14'
ABI: 'arm64'
pid: 4259, tid: 4259, name: oid.inputmethod  >>> com.sec.android.inputmethod <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2
Cause: null pointer dereference
    x0   0000000000000002  x1   000000732f216004  x2   00000000000003f3  x3   0000007350614018
    x4   000000732f216004  x5   000000732f216000  x6   342cfb9c325c2e5f  x7   8caec0c00850a39e
    x8   77eca4df4ac4bde4  x9   3e79aa2be9db592e  x10  0000000000000000  x11  0000000000000067
    x12  0504d1bbc5ebf0f2  x13  325c2e5f59daf299  x14  0000000000000004  x15  fffffffffffffffe
    x16  00000073537b42c8  x17  0000007353707e50  x18  000000007ff00000  x19  0000007350614018
    x20  0000000000000001  x21  0000000000000002  x22  ffffffffb5f72d67  x23  00000000000003f3
    x24  ffffffffb5f72d67  x25  00000000000003f3  x26  0000007fcb37cf51  x27  0000007355d29a60
    x28  0000000000000009  x29  0000007fcb37caa0  x30  000000735375edc8
    sp   0000007fcb37ca60  pc   0000007353707fe8  pstate 0000000080000000
backtrace:
    #00 pc 000000000001dfe8  /system/lib64/libc.so (memcpy+408)
    #01 pc 0000000000074dc4  /system/lib64/libc.so (fread+220)
    #02 pc 00000000000290d0  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #03 pc 00000000000276c4  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #04 pc 00000000000275a8  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #05 pc 000000000001d52c  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #06 pc 00000000000207ac  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #07 pc 000000000001fea4  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #08 pc 0000000000029ba8  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x1ca0000)
    #09 pc 00000000002105fc  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x11e7000)
    #10 pc 0000000000103e64  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x11e7000)
    #11 pc 000000000011467c  /system/app/SamsungIMEv3.0/SamsungIMEv3.0.apk (offset 0x11e7000)
    #12 pc 0000000001d364e0  /system/app/SamsungIMEv3.0/oat/arm64/SamsungIMEv3.0.odex (offset 0x704000)

Nexus 5, Android 6.0.1, Support Lib 26.1.0. Still crashing!!!!

@20 What about 27.0.0 ? For now we don't use it because of a different issue:
https://issuetracker.google.com/issues/68969155

Started getting crashes on LG G3 with Android 5.0 after upgrading support library from 25.3.1 to 26.1.0

As we have not observed the issue on 27.0.1 closing it. If you come across the issue on the latest version, please let us know by raising a new issue.

@23 You haven't tried enough, then, or tried on the wrong devices and Android versions.
Succeeded again in less than 10 seconds on OnePlus 2 with version 27.0.1 ...
Here's a new issue, as you've requested:
https://issuetracker.google.com/issues/69593710

I really don't get you guys. Why do you close issues so fast? You couldn't even reproduce it on previous versions, yet we all could.

this bug still exist in API 27.0.2
Samsung Galaxy J5 2016, Android 6.0.1

create a recycler view with checkbox and have a custom statelistanimator for the checkbox. now keep toggling the checkbox rapidly and you will see this crash.

Maybe it helps to someone, but there is another way to avoid this crash without setting android:stateListAnimator="@null"
Just need to set animation duration to 0 for default StateListAnimator of AppBarLayout by adding following string to your values.xml:

        <integer name="app_bar_elevation_anim_duration" tools:override="true">0</integer>

Or you can create your own StateListAnimator like here https://android.googlesource.com/platform/frameworks/support/+/master/design/lollipop/android/support/design/widget/ViewUtilsLollipop.java
P.S. checking "view" for not null in ViewUtilsLollipop.setDefaultAppBarLayoutStateListAnimator can be possible solution for this issue. It's a pity that the issue is closed

@27 I don't see any issue with android:stateListAnimator="@null", though. I don't even see it affects anything at all in this case.

another solution is:
```xml
<android.support.design.widget.AppBarLayout
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    app:elevation="any dp"> <!-- no android:elevation -->
...
</android.support.design.widget.AppBarLayout>
```

Version info for #29:
    implementation 'com.android.support:appcompat-v7:26.1.0'
    implementation 'com.android.support:design:261.0'

Why was it closed? I still can reproduce it on API 27.0.2 and Android 5.0.

@31 No idea. Can you please create a new one, and put a link to it here?

There has been quite a few closed like this where no solution is mentioned and it's still reproducible.  I question their internal processes.

OK, I've created a new issue here:
https://issuetracker.google.com/issues/72614327

I have the same issue on Samsung Galaxy S6 Android 6.0.1. Support library version 27.0.2.
Any plans to fix it?

@35 I think now it's fixed. I can't reproduce it anymore:
https://issuetracker.google.com/issues/69593710#comment5